Add eol warnings

[runesoerensen]

Summary

• Migrate resolve-version to use shared types (NodejsInventory, NodejsArtifact, VersionRange) from the nodejs-data crate being extracted in Extract shared Node.js types into nodejs-data crate buildpacks-nodejs#1328, replacing local parallel implementations
• Derive the default Node.js version and LTS major version from the upstream release schedule instead of hardcoding them, and warn when a resolved version has reached end-of-life - mirroring and leveraging the CNB work in Implement EOL warnings and derive default node version from release schedule buildpacks-nodejs#1352

Commit progression

This draft PR contains two commits mostly because it's intended as a PoC, but they could be split into separate PRs before merging.

bca6a31 - Use nodejs_data from the CNB in resolve-version

Adopts the shared nodejs-data crate from the ccasey/nodejs-data-crate branch. Replaces the local Requirement struct and NodeInventory/NodeArtifact type aliases with VersionRange, NodejsInventory, and NodejsArtifact from the shared crate. The wide-range/LTS-bound resolution logic stays local for now, bridging to node-semver types via VersionRange's Display output.

40dbd3d - Derive LTS version from release schedule and warn on EOL Node.js versions

Switches the nodejs-data dependency to the implement-eol-warnings-v2 branch to pick up NodeReleaseSchedule types. Adds inventory/schedule.json (from the upstream Node.js release schedule) and changes the resolve-version CLI to accept a schedule path instead of a hardcoded LTS major version. The binary now:

• Derives the newest supported LTS from the schedule (removing the hardcoded lts_major_version="24" from the shell scripts)
• Makes [node_version] optional — when omitted, defaults to the newest supported LTS
• Returns an EOL warning in the JSON output when the resolved version has passed its end-of-life date

Also adds an output::warning function to lib/output.sh for styled warning output.

Follow-up

• A separate follow-up PR will move the wide-range/LTS-bound resolution logic into the shared nodejs-data crate, removing the node-semver bridge code in resolve-version.
• Add a GitHub action similar to the one in Implement EOL warnings and derive default node version from release schedule buildpacks-nodejs#1352 that updates the inventory/schedule.json file.

[colincasey]

closing this in favor of the stacked changes for #1621