chore: upgrade Node-RED to 5.0.0 and Docker base image to Node.js 24

[devin-ai-integration]

Summary

Upgrades the Node-RED runtime to the latest release (5.0.0) and bumps the Docker base image to Node.js 24.

• .docker/Dockerfile.alpine: ARG NODE_VERSION=16 → ARG NODE_VERSION=24 (builds on node:24-alpine).
• package.json: node-red 3.1.0 → 5.0.0. Node-RED 5 requires Node.js >=22.9, so engines.node is bumped >=14 → >=22.9 to match.
• package-lock.json: regenerated so the npm ci step in the Dockerfile stays in sync with the new dependency tree.

Based on feature/layout since that is the branch that actually contains the Dockerfile, package.json, and app sources (main/development only hold LICENSE + README.md).

Verification

Built and ran the image locally:

docker build -f .docker/Dockerfile.alpine -t node-red-docker:test-alpine .   # succeeds on node:24-alpine

Container logs confirm the upgrade is functional:

[info] Node-RED version: v5.0.0
[info] Node.js  version: v24.16.0
[info] Started flows

Note (pre-existing, not addressed here): .docker/scripts/entrypoint.sh is committed without the executable bit (git mode 100644) and the Dockerfile never chmods it, so the image fails with exit 126 when started via the default ENTRYPOINT. This is unrelated to the version bump (verified by invoking the entrypoint manually, output above). Happy to fix in a follow-up if desired.

Link to Devin session: https://app.devin.ai/sessions/7af11e7d8d2d4b2b8425e417b5f3d5df
Requested by: @ymedlop

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring