feat(sm): reference architeture link updates

[leiicamundi]

Description

InfraEx is consolidating all the reference architectures in a single repository: https://github.com/camunda/camunda-deployment-references

This PR address relocation of the content from the old repos to the new one.
As some links were already using the new repo, this PR should be merged when a documentation release is planned as the PRs below will be break the existing live doc when merged.

To be replaced after each PR is merged

SM changes:

• PR Integrate ROSA repo in the reference arch camunda-deployment-references#120 => stable/8.6
• PR feat(rosa-single-region): integrates 8.7 camunda-deployment-references#132 feature/rosa-8.7 => main
• PR feat(rosa-single-region): integrates 8.8 camunda-deployment-references#134 feature/rosa-8.8 => will remain unmerged, we will wait until 8.7 is released to integrate it

TODO

• Align with @camunda/tech-writers to release a doc release when this PR is merged, otherwise existing doc will break

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 an upcoming minor release and:
  • are in the /docs directory (version 8.8).
  • are in the /versioned_docs/version-8.7/ directory (version 8.7).
• My changes are for an already released minor and are in a /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]

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

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.

• docs/self-managed/setup/deploy/amazon/aws-ec2.md
• docs/self-managed/setup/deploy/amazon/openshift/terraform-setup-dual-region.md
• docs/self-managed/setup/deploy/openshift/dual-region.md

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.7/.

• docs/self-managed/setup/deploy/amazon/aws-ec2.md

These files were changed only in versioned_docs/version-8.7/. You might want to duplicate these changes in docs/.

• versioned_docs/version-8.7/self-managed/zeebe-deployment/configuration/broker.md
• versioned_docs/version-8.7/self-managed/zeebe-deployment/configuration/gateway.md

These files were changed only in versioned_docs/version-8.7/. You might want to duplicate these changes in versioned_docs/version-8.6/.

• versioned_docs/version-8.7/self-managed/setup/deploy/amazon/openshift/terraform-setup-dual-region.md
• versioned_docs/version-8.7/self-managed/setup/deploy/openshift/dual-region.md

These files were changed only in versioned_docs/version-8.6/. You might want to duplicate these changes in docs/.

• versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/broker.md
• versioned_docs/version-8.6/self-managed/zeebe-deployment/configuration/gateway.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.

[Langleu]

Leaving my initial feedback on this.
Mostly links being 404.

[Langleu]

leaving this as a single comment for the file to switch it to main for the next version.

[Langleu]

had a quick look over the rendered docs and the bash references seem to all be in place properly except for the ones not working with 404.

[conceptualshark]

Running through the links and formatting, everything seems to have been resolved/works well for me, so I think this PR will be ready to merge when you are. Would you like a hold label on it to ensure it isn't merged in advance?

Happy to approve and coordinate a specific release for you if you need to time it with the other repo, just let me know!

[Langleu]

Just one small comment which isn't hindering a merge or so.
Had a quick check with lychee --include-verbatim and seems like all 404 were resolved 🚀.

[github-actions]

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