Use nodejs-wheel to install node

[mvdbeek]

nodeenv has various issues like ekalinin/nodeenv#388, and fetching the node installation via pypi seems easier for packaged galaxy as well.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[nsoranzo]

Should we drop the actions/setup-node@v5 steps in CI workflows?

If we do, then we can also drop the client/.node_version file and relax nodejs-wheel==22.13.0 to ==22 in both packages/app/setup.cfg and pyproject.toml . This way we can have weekly nodejs minor-version updates handled by uv.

[mvdbeek]

We still use .node-version in some of the actions that we can't remove, but I think removing it wherever we do install python dependencies is a good idea.

[github-actions]

This PR was merged without a "kind/" label, please correct.