feat: Node.js 22.23.2

[nodejs-github-bot]

Automated changes by create-pull-request GitHub action

[MikeMcC399]

This PR could be processed on its own, although the title should be changed to include the Node.js version 22.23.2.

I suggest however to hold this back until the other parts of the July 2026 security release have caught up.

Node.js 26.5.1 is already available, but without a musl build yet.

Node.js 24.18.1 is still completely missing.

[PeterDaveHello]

I'm not sure how long we'll have to wait this time. Based on past experience, there can be a significant time gap between unofficial builds of different versions.

That is why we've previously moved ahead with merging updates from various versions, but since every situation is unique, it might be worth waiting a bit longer this time.

[MikeMcC399]

I've just been informed that 24.18.1 is available now. I'm able to install it locally as a cross-check.

[MikeMcC399]

There are two options right now:

1. Run ./update.sh -s locally to produce updates for 22, 24 & 26, then manually create a PR, but drop the changes for alpine OR
2. Wait for musl builds to complete and let the automation update the PR

If the musl builds have not caught up by tomorrow morning UTC timezone, I would in any case go ahead manually without them.

[nschonni]

I don't think we need to wait to land this. If the bot starts opening more PRs before it's landed upstream, it just get's added to that open PR.
The buildout on their side is also heavy so their is no benifit to waiting for all the releases I don't think

[MikeMcC399]

I have to drop out for today, so please just carry on with your best judgement! I hope to be available tomorrow again!

Unblocking for bot to open new PRs later

[github-actions]

Created PR on the official-images repo (docker-library/official-images#21944). See https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what if you are wondering when it will be available on the Docker Hub.