Broken test for labeled statements
When we convert a LabeledStatement to HIR we can end up emitting "consecutive" blocks, ie where there are two blocks such that control flow will always go from from one block to the other, with no other way to reach the second block but through the first. Example: ```javascript label: { foo(); break label; } bar(); ``` Converts to ``` bb0: foo() goto bb1: bb1: bar(); ... ``` Ideally in this case we would merge these into a single block: * When debugging, the extra goto makes it look like there is conditional control flow when there isn't. If the code is consecutive it's easier to understand that if it's a single block. * Conversion from HIR -> AST relies on consecutive code all being in a single block, so this breaks codegen (we never visit the goto target since all gotos are assumed to be safe to convert to a break or continue). This PR adds a failing test case, the next PR fixes it.