chore: update node to v22

[pepopowitz]

Description

Bumps the version of node to something actually supported (current lts)

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.

• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

• My changes require a docs infrastructure review.

[pepopowitz]

build-docs and check-format succeed on this PR, with the upped node version. The other two affected workflows - publish-stage and publish-prod -- we will have to wait until this one merges to test.

But I think this is good to go!

[github-actions]

The preview environment relating to the commit 70a5553 has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-4667/index.html