[Jumpy Platformer] Switching from Python to Blocks generates "_initActionKind" error

[Nina-1210]

Describe the bug
In the Jumpy Platformer tutorial under Blocks Games, an error is generated after switching the project from Blocks to Python and then back to Blocks.

Steps to reproduce the behavior:

1. Navigate to Microsoft MakeCode Arcade
2. Open Jumpy Platformer tutorial under Blocks Games.
3. Switch the editor from Blocks to Python.
4. Switch back from Python to Blocks.
5. Observe the editor and the Problems panel.

Actual behavior
The Problems panel displays the error: Property '_initActionKind' does not exist on type 'typeof ActionKind'.

Expected behavior
No warning blocks or compilation errors should appear after switching from Python back to Blocks.

Screenshots

Additional context
1.OS: Windows11 25H2
2.Browser: Chrome, Edge and Firefox
3.arcade version: 4.1.18
4.Microsoft MakeCode version: 13.1.17

[Nina-1210]

Possibly related to #6749, as both issues occur when switching between Python and Blocks. However, the resulting error is different.

[abchatra]

Nina-Wang (@Nina-1210) can you check if this is a regression from last version arcade.makecode.com/v3?

[Nina-1210]

Nina-Wang (@Nina-1210) can you check if this is a regression from last version arcade.makecode.com/v3?

Abhijith Chatra (@abchatra) the issue is not a regression, and still repro's on arcade.makecode.com/v3.