rename test-dev-bug-xxx refs to test-bug-xxx

doc/testcases.txt

@@ -154,7 +154,7 @@ there is currently no tracking of specification coverage.
 Test cases starting with ``test-dev-`` are development time test cases
 which demonstrate a particular issue and may not be very well documented.
 
-Test cases starting with ``test-dev-bug-`` illustrate a particular
+Test cases starting with ``test-bug-`` illustrate a particular
 development time bug which has usually already been fixed.
 
 Duktape API test cases

src/duk_js_call.c

@@ -1797,7 +1797,7 @@ void duk_handle_ecma_call_setup(duk_hthread *thr,
 		 *  Although the callstack entry is reused, we need to explicitly unwind
 		 *  the current activation (or simulate an unwind).  In particular, the
 		 *  current activation must be closed, otherwise something like
-		 *  test-dev-bug-reduce-judofyr.js results.
+		 *  test-bug-reduce-judofyr.js results.
 		 */
 
 		DUK_DDDPRINT("is tailcall, reusing activation at callstack top, at index %d",

src/duk_js_compiler.c

@@ -4582,7 +4582,7 @@ static void parse_switch_statement(duk_compiler_ctx *comp_ctx, duk_ivalue *res,
 		 *  Note that there may be no code at all, not even an empty statement,
 		 *  between case clauses.  This must be handled just like an empty statement
 		 *  (omitting seemingly pointless JUMPs), to avoid situations like
-		 *  test-dev-bug-case-fallthrough.js.
+		 *  test-bug-case-fallthrough.js.
 		 */
 
 		num_stmts = 0;
@@ -4974,7 +4974,7 @@ static void parse_try_statement(duk_compiler_ctx *comp_ctx, duk_ivalue *res) {
 		 *  within the catch clause work correctly.  This restriction should
 		 *  be fixable (at least in common cases) later.
 		 *
-		 *  See: test-dev-bug-catch-binding-2.js.
+		 *  See: test-bug-catch-binding-2.js.
 		 *
 		 *  FIXME: improve to get fast path access to most catch clauses.
 		 */