Update the recommended version upgrade path

[conceptualshark]

Description

Specify that prior to 8.4, the Helm chart upgrade path is to the latest patch of the next minor version.

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.

[aabouzaid]

@conceptualshark What do you think about giving an example here?
So, adding something like:

For example, If the current Helm chart version is 10.x.x and the latest next major version is 11.0.1, then it's recommended to upgrade to 11.0.1, not 11.0.0.

But that's just a suggestion and it's up to you.

[mesellings]

Lgtm - only a non-blocking suggestion for rewording 👍

[mesellings]

Suggested change

	To upgrade to a more recent version of the Camunda Helm charts, there are certain things you need to keep in mind. Review the [instructions for a specific version](#version-update-instructions) before starting the actual upgrade.
	Before upgrading to a more recent version of the Camunda Helm charts, you should review the [instructions for a specific version](#version-update-instructions).

Just a rewording suggestion for conciseness - wasn't sure whetehr to use "should" or "must" either?