Run enclosing finally when break/continue jumps out of a try block

[ASDAlexander77]

Summary

Fixes the follow-up tracked as item 5b in docs/LowerToAffineLoops-LowerToLLVM-review.md (found while testing #233): break/continue inside a try body or catch clause jumped straight to the loop's continuation/increment block, silently skipping the enclosing finally.

Fixed the same way return in try/finally already worked, per the repo owner's suggestion:

• Escape detection: TryOpLowering collects BreakOp/ContinueOp ops in the body/catches that already have a tsContext->jumps entry at try-lowering time. That's a clean discriminator for "jumps out of this try" — the target loop/label encloses the try, so its lowering (which populates jumps) ran first in the pre-order worklist, while jumps targeting a loop inside the try aren't resolved yet.
• Routing: for each distinct escape target, the finally region is cloned once (mirroring the existing return-cleanup clone), the clone is terminated with a branch to the original target, and jumps[op] is re-pointed at the clone. BreakOpLowering/ContinueOpLowering need no structural change — they just branch into the finally copy, which continues to the real target.
• Nested try/finally chains compose naturally: the outer try lowers first and re-points the op at its finally copy; a nested try later re-points the same op at its copy, which branches to the outer copy — finallys run innermost-first.
• Catch clauses: escaping jumps inside a catch additionally set unwind[op], and the break/continue lowerings now emit EndCatchOp when it's set, mirroring return-from-catch.

Test plan

• ctest --test-dir __build/tslang/windows-msbuild-2026-debug -C Debug -j8 — 690/690 passed (JIT + AOT)
• 00try_finally_break_continue.ts extended with: break in try body, continue in try body, two-level nested finally chain (both finallys run), break from a catch clause (catch + finally + EndCatch), one try with both a break and a continue escaping (two distinct targets → two separate finally copies), and a negative case (break of a loop fully inside the try is not rerouted — finally runs exactly once)
• Each scenario verified by JIT execution with value-checked asserts before being formalized into the test file