ECC-2241: MTG2Switch rules extension required for IFS cycle CY50R1

[mjg41]

Description

The MTG2Switch functionality for cy50r1 currently enforces a tablesVersion value of 35 to be pre-mtg2, otherwise the data is formed as post-MTG2. Data has already been produced as cy50r1 with tablesVersion 34, and tablesVersion 36 will be released imminently. To this end we should extend the 50r1 switch functionality to include tablesVersion 34 and 36.

For this to be used by IFS, a hotfix would be needed on top of 2.44, which is what the ifs-bundle uses in cy50r1, so a 2.44.3. This development would also be included in 2.46.1 to be in the mars client and server bundles that will be used for 50r1.

Contributor Declaration

By opening this pull request, I affirm the following:

• All authors agree to the Contributor License Agreement.
• The code follows the project's coding standards.
• I have performed self-review and added comments where needed.
• I have added or updated tests to verify that my changes are effective and functional.
• I have run all existing tests and confirmed they pass.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (hotfix/2.46.1@dde9f28). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             hotfix/2.46.1     #437   +/-   ##
================================================
  Coverage                 ?   88.51%           
================================================
  Files                    ?      849           
  Lines                    ?    63104           
  Branches                 ?    11226           
================================================
  Hits                     ?    55856           
  Misses                   ?     7248           
  Partials                 ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.