feat(versioning): Add a NodeJS Lambda Versioning module

[Garethp]

Changes

This PR adds a versioning module for NodeJS Lambda Runtimes provided by AWS

Context

As discussed in this discussion, I want to keep versions of Node in with the release schedule of AWS Lambdas. AWS NodeJS Lambdas release within a month or two after a NodeJS version goes LTS so there is a period of time where a version of Node is LTS but not available as a Lambda Runtime. To keep a project's node dependency on the same version as the Runtime it will run on, I need to be able to set those dependencies (nvmrc, docker etc...) to follow the Lambda Runtime release schedule rather than the NodeJS release schedule.

Since this is meant to be a drop-in replacement for any packages that follow node versioning, I've re-used most of the functions provided by the node versioning module and only changed the isStable function.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[viceice]

needs code coverage

https://github.com/renovatebot/renovate/actions/runs/11800328119/job/33317532023#step:6:22

[github-actions]

Hi there,

This PR appears to have been inactive for a while. Please let us know if you are still working on it, or if we can close it for now.

Thanks, the Renovate team

[Garethp]

@viceice, I've removed the unused code and changed how I'm mocking the data. I've also mocked out dataFiles so that I can test some of the if conditions that are based on unstable data from the datasource. Let me know if this is the appropriate way of testing that instability.