Deprecate node 20 and change testing matrix to node 22, 24 & 25

[kriswest]

It time to update the testing matrix and node versions used in FDC3 workflows. We are currently using Node 20 but:

• Node 20 will be EOL at the end of the month
• Node 22 is already in maintenance, and will remain in use for at least another year
• Node 24 is the current LTS release
• Node 25 has just moved into maintenance
• Node 26 will be the current release by the end of the month

Update single version workflows to use Node 24, and the testing matrix to cover 22, 24 and 25. A subsequent issue should replace node 25 with 26 when it is released.

[snakefood3232]

I'll handle this node version update. Since Node 20 is EOL at month's end, we need to shift to the supported versions you outlined.

My approach:

• Update all single-version workflows (like build/release) to use Node 24 (current LTS).
• Modify the testing matrix in CI to run against Node 22, 24, and 25 as specified.
• Ensure all package.json engine fields and any version checks are updated accordingly.

I can have this completed and a PR ready for review within 1-2 days. This will keep the project on supported versions ahead of the EOL deadline.

[kriswest]

We discussed this at #1856 and think we don't actually need the matrix and can just test under Node 24. However, we intend to support Node 22 upwards and think we should set the engines fields (not currently set) to 22.