Fixing test_routing_pybind workflow failures

[mattw-nws]

See comment in #519 and discussion in #524 , rolls back some changes in 7550dfc to fix failing tests, and excludes pyarrow 12.0.0 because of apache/arrow#15054 (v11.0.0 doesn't have the behavior and hopefully 13.0.0 will fix it).

Additions

Removals

Changes

• rolled back pathing changes in 7550dfc in ngen_routing_config_unit_test.yaml
• updated workflow YAML to exclude pyarrow version 12.0.0 specifically

Testing

Screenshots

Notes

Todos

• Make sure when pyarrow 13.0.0 is released that the segfault bug goes away.

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
• Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• Reviewers requested with the Reviewers tool ➡️

Testing checklist (automated report can be put here)

Target Environment support

• Linux
• macOS

[program--]

This looks good to me!

I think this brings up something we need to account for when dealing with config files -- if ngen is available via PATH, then we may want to handle configuration paths as relative to the configuration file (as opposed to relative to the user's cwd, if it does exhibit this behavior), or at least document a defined behavior (if it is not documented already paths being relative to the executable is documented here), but that's for a different discussion :)

[mattw-nws]

Yes, it would be particularly nice for configuration files with paths in them to be able to handle paths as relative to the parent file--in this case you'd have to file that issue with NOAA-OWP/t-route 😄 . Interestingly, however, we also generate realization config "files" as strings in some of our tests... so that becomes an edge case that would add some complexity.