feat: auto-fetch node versions in module extension

[gzm0]

More aggressive alternative to #3916: We even do the fetching if facts are not available.

PR Checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature (please, look at the "Scope of the project" section in the README.md file)
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Node versions / digests are hardcoded and shipped with rules_nodejs.

What is the new behavior?

rules_nodejs retrieves required Node digests as needed and stores them in facts or in generatedRepoSpecs in the bzlmod lockfile.

Does this PR introduce a breaking change?

• Yes
• No

Other information

• feat: use facts to auto-retrieve node versions if possible #3916 (fact only alternative)
• Example lockfile with bazel 8.1.0
• Example lockfile with bazel 9.1.1

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 26e0a05fdf

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[jbedard]

I think this LGTM, are you in favour of merging this one over #3916?

[gzm0]

Yes, I'm in favor of this one.