feat: update node toolchain to provide File objects

[gregmagolan]

To-date the node toolchain has provided paths (strings) to node and npm. This complicates downstream usage as they need to convert these paths depending on they are used (between execpath and rootpath for example). This change configures the toolchain to also provide File objects for node and the npm entry point script so downsteam uses can choose to get either the .path or .short_path as needed.

Deprecates target_tool and target_tool_path parameters. Maintains backward compat by setting both target_tool_path and tool_files in the provider.

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?

• Feature (please, look at the "Scope of the project" section in the README.md file)

Does this PR introduce a breaking change?

• Yes
• No

[jbedard]

LGTM, but if we are avoiding breaking changes how will other rulesets take advantage of this? Especially if we still want to support the *_path options everywhere won't we still have the same path vs short_path problem?

[gregmagolan]

LGTM, but if we are avoiding breaking changes how will other rulesets take advantage of this? Especially if we still want to support the *_path options everywhere won't we still have the same path vs short_path problem?

rules_js will need to be both backward and forward compatible; preferring the Files in the provider over the paths if they are there. Can't have your cake and eat it too without breaking changes.

[gregmagolan]

In the future when we drop WORKSPACE support here and in rules_js then all of this is unwound and removed.

I'm hoping to be bzlmod only in all of our rule sets after Bazel 8 is released.