clarify 10.0.2 helm chart upgrade path

[conceptualshark]

Description

Resolves #4640

Initial internal report/suggestion

A customer upgrading from v9.x.x did not interpret the existing requirement of "10.0.2+" as inclusive of v10.4.5. However, any v10.x.x > 10.0.1 can be used to upgrade from v9.x.x.

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.

[akeller]

I think this is more descriptive, but I can't pinpoint what else might be missing.

We announced this in the 8.5 docs, which made me wonder how long we maintain a Helm chart version or what version we expect users to be on for 8.6 and 8.7.

[mesellings]

Lgtm - 👍 🚀

Only non-blocking suggestions would be:

• Perhaps make the last two sentences into a list, so it is easier to scan/read?
• Make these two sentences active voice/address the reader directly?

e.g.
The upgrade path for Camunda Helm Chart v9.x.x is to the latest patch version of v10.

• You can use any minor or patch version after (and including) 10.0.2.
• You cannot upgrade from v9.x.x to v10.0.0 or v10.0.1.

[conceptualshark]

@mesellings I've added some of your suggestions here! Do you mind re-reviewing?

[mesellings]

Lgtm - nice job! 🚀 👏