Fix backwards compatibility issue

[JordanLaserGit]

Restores backward compatibility with older datastream containers (issue #103): t-route restart/crosswalk args are now handed to datastream config gen, bmi-config-gen, and validation steps via environment variables instead of CLI flags, so older containers ignore them rather than erroring on unrecognized arguments. Also adds a manual workflow to test deployed container combinations.

Additions

• Manual-dispatch workflow .github/workflows/test_datastream_backward_compatibility.yaml that runs the datastream against each deployed DS/FP/NGIAB combination, or a custom combo passed as inputs.

Removals

• --troute_restart/--troute_crosswalk(_file) CLI flags from the configure_datastream.py, ngen_configs_gen.py, and run_validator.py docker invocations.
• Redundant RESTART_BASE branching in the ngen config-gen step.

Changes

• scripts/datastream passes t-route restart/crosswalk to those three steps via docker run -e env vars.
• configure_datastream.py, ngen_configs_gen.py, and run_validator.py default those args from the corresponding env vars.

Testing

1. Actions → "Test Datastream Backward Compatibility" → Run workflow.

Screenshots

Notes

The docker version combinations that are used in the NRDS are hardcoded into the workflow. It'll accept another combination as args, but that combinations structure will ideally be updated with NRDS releases.

Todos

• Update CHANGELOG "Unreleased" section.

Checklist

• PR has an informative and human-readable title
• Changes are limited to a single goal (no scope creep)
• Code can be automatically merged (no conflicts)
• Code follows project standards (link if applicable)
• Passes all existing automated tests
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future todos are captured in comments
• Visually tested in supported browsers and devices (see checklist below 👇)
• Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• Reviewers requested with the Reviewers tool ➡️

Testing checklist

Target Environment support

• Windows
• Linux
• Browser

Accessibility

• Keyboard friendly
• Screen reader friendly

Other

• Is useable without CSS
• Is useable without JS
• Flexible from small to large screens
• No linting errors or warnings
• JavaScript tests are passing

[quinnylee]

What a neat bash operator trick. I'm stealing this

[quinnylee]

This link doesn't point to anything. Was this file meant to be added to this PR?

[JordanLaserGit]

This is why I shouldn't dev at night. Meant to push this to a different branch... 🙃

[JordanLaserGit]

#108

[quinnylee]

Overall looks like a good PR. All the pytests are passing locally, and the failing CI test seems to be unrelated to this change. Only change I would want is in the README addition that doesn't point to an existing markdown file.