docs: mention docker tag change in upgrade

[OmranAbazid]

Description

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.

[github-actions]

👋 🤖 🤔 Hello! Did you make your changes in all the right places?

These files were changed only in optimize/. You might want to duplicate these changes in optimize_versioned_docs/version-3.13.0/.

• optimize/self-managed/optimize-deployment/migration-update/3.13_8.5-to-3.14_8.6.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[christinaausley]

Hi @OmranAbazid -- can you add a description or link the related issue for this PR? Would you like this to go out with the alpha next week?

[OmranAbazid]

Hi @christinaausley
This is only needed for the next minor.
Here is thr parent issue:
https://github.com/camunda/camunda-optimize/issues/13498

[OmranAbazid]

@christinaausley Can you please approve this to be able to merge it.

[akeller]

@OmranAbazid, just a heads up: if we merge this, it will be available publicly as early as this week or with alpha5 changes. Is that OK?

[OmranAbazid]

@OmranAbazid, just a heads up: if we merge this, it will be available publicly as early as this week or with alpha5 changes. Is that OK?

@akeller Yea, I think that is fine. I guess it will be available when a user click on the "next" version