Add the Helm version matrix to supported environments

[conceptualshark]

Description

Resolves

#4915 (comment)

There was a request made in this PR to have a version of the Helm chart matrix in the supported environments page, specifically because the camunda-platform-helm version matrix links all versions, including those not in active support.

This PR has two options - the original request/suggestion, with the Helm chart links in a column for the component matrix, and a version where only Camunda version and Helm chart version is listed under the Self-Managed section. I think this second version might be more appropriate, as it doesn't suggest that Helm is the only method for working with those components, and also doesn't reuse or confuse "Deploy" as terminology (open to other names for that column!), or make that table additionally busy.

When should this change go live?

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

PR Checklist

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

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[github-actions]

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

[christinaausley]

I think this second version might be more appropriate, as it doesn't suggest that Helm is the only method for working with those components, and also doesn't reuse or confuse "Deploy" as terminology (open to other names for that column!), or make that table additionally busy.

Agreed on this @conceptualshark! This looks great.

[conceptualshark]

@christinaausley Thank you! I've cleaned this up to just the one option, if you are able to review. 👍

[github-actions]

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