Issues #778 and #779 - #846 - #846

Description

This PR fixes two OpenSCENARIO Init-section semantics issues:

• Init actions must complete before storyboard triggers can start competing event actions.
• TeleportAction must not claim longitudinal or lateral control domains.

Closes #778
Closes #779

Changes

• Move trigger evaluation in StoryBoard::Step until after the Init global, user-defined, and private actions have stepped.
• Set TeleportAction to DOMAIN_MASK_NONE, matching the OpenSCENARIO action-domain table.
• Add a minimal .xosc regression scenario that combines an Init TeleportAction, an Init step SpeedAction, and an immediately triggered event SpeedAction.
• Add GTest coverage for the TeleportAction domain mask and smoke-test coverage for the Init-action ordering.

Testing

1. Reproduced both failures against 19d26b6 using init_instantaneous_actions.xosc:
   • Stopping Init Car TeleportAction on conflicting Lateral & Longitudinal domain(s)
   • Stopping Init Car LongitudinalAction on conflicting Longitudinal domain(s)
2. Verified the same scenario after the fix: both Init actions complete before EventSpeedAction starts and no Stopping Init Car conflict warning is emitted.
3. Ran TeleportActionTest.DoesNotClaimLongitudinalOrLateralControl: passed.
4. Ran TestSuite.test_init_instantaneous_actions: passed.
5. Ran XML/Python syntax checks, git diff --check, clang-format 15.0.7, Cppcheck 2.17.1, and a minimal MSVC build: passed.
6. Ran a real OpenSCENARIO/OpenDRIVE scenario from the local simulation dataset: completed successfully.