Update ngen-build Github Action to make sure 1.x numpy is used

[robertbartel]

Updating Actions depending on numpy install to use pre-2.0 numpy version. Currently, CMake will raise an error if the found numpy version is >= 2.0.0.

Changes

• Update "Get Numpy Python Dependency" of internal ngen-build action to make pip installed numpy<2.0.0

Notes

This is going into the pending release-0.3.0 branch. The included changes will eventually make their way into production and master as part of other steps in the release process.

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 ➡️

Target Environment support

• Linux (Ubuntu 22.04 Action runner)
• MacOS (MacOS 12 Action runner)

[aaraney]

This doesn't stop a downstream workflow from requesting numpy>=2.0.0 via inputs.additional_python_requirements. IMO that is desirable. This seems like an appropriate place to use constraints.txt. We should be able to enforce this behavior in all downstream workflows by setting the PIP_CONSTRAINT environment variable to the constraints file.

[robertbartel]

I'm pretty sure that changes to actions within a PR aren't applied when actions are run for the PR. So we should expect to still see the failures in the checks that this PR is intended to address.

Someone correct me if I'm wrong though.

[robertbartel]

This doesn't stop a downstream workflow from requesting numpy>=2.0.0 via inputs.additional_python_requirements.

Yeah, good catch @aaraney. I've modified the approach.

I wanted to use an absolute path, and for lack of a more obvious place, I put the file in the root directory. Sanity check me to make sure I'm not failing to think of a good reason we should avoid that (or just a good reason to put it somewhere else).

[aaraney]

This looks great! Thanks @robertbartel