fix: prevent infinite loading loop in Frostbite Caves (fixes #17)

[Lordfckx]

Summary

• Fixes Indefinite time while loading the map for the FrostBite Caves #17 — "Indefinite time while loading the map for the FrostBite Caves"
• Removed a premature return keyword in the switchWM generator that caused flowerOff() to be skipped, leaving the loading animation stuck forever

Root Cause

In worldMapScene.ts (switchWM method), the load callback generator had:

case 0: ... if(!p){i.next=18;break}return p.MapProps=h, ..., p.init();

The raw return exited the generator immediately, bypassing case 19 where flowerOff() is called. This left the loader flower visible indefinitely — appearing as an "infinite loading loop."

Fix

Removed return so execution falls through to subsequent cases:

Before: !p){i.next=18;break}return p.MapProps=h
After:  !p){i.next=18;break}p.MapProps=h

Now p.init() → case 16 → case 19 → flowerOff() is always reached.

Testing

• JavaScript syntax validated (no broken structure, all System.register / _RF.pop counts preserved)
• Frostbite Caves level data (IceageWORLDMAP) confirmed valid — all 42 levels, no corrupted JSON
• HTTP server starts without errors
• The fix affects the shared switchWM code path, so it benefits all worlds, not just Frostbite Caves

Note

This is a patch to the compiled docs/assets/main/index.js. The original TypeScript source was not available, so the equivalent TS fix would be removing the return before this.currentWM = p; p.MapProps = h; ... p.init(); in worldMapScene.ts:switchWM.

[sourcery-ai]

Sorry @Lordfckx, your pull request is larger than the review limit of 150000 diff characters