add nodejs sdk to overview page

[christinaausley]

Description

Closes #4782.

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.

[mesellings]

Lgtm 👍 🚀

One non-blocking issue that perhaps is just something to look at when we move to docusaurus 3 is that the card height is dependent on the text content - here the node card is now taller than the one next to it:

I would expect card components to behave slightly differently ideally, but I guess our options are:

1. Adjust the meta description for the node.js page, i.e. remove ", available via npm.", except this then conflicts with SEO description length.
2. Leave as is, take a look at card components in Docusaurus 3.

I guess we shouldn't be trying to fit content to a responsive layout, so I think 2 is our best option, but up to you - just something I noticed?

[christinaausley]

@mesellings Good catch. This was bothering me so for the time being I adjusted the description length, as it isn't dire either way. Cheers to Doc3 when this perhaps won't be an issue?

[mesellings]

Lgtm 👍 🚀

[github-actions]

🧹 Preview environment for this PR has been torn down.