doc(self-managed): improve multiregion self-managed readability

[leiicamundi]

Description

This PR aims to improve readability of the self-managed multi-region documentation by adding tables and refactoring some parts.

When should this change go live?

It should not be merged until #4205 is merged.

• 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 docs/. You might want to duplicate these changes in versioned_docs/version-8.5/.

• docs/self-managed/concepts/multi-region/dual-region.md
• docs/self-managed/operational-guides/multi-region/dual-region-ops.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.

[mesellings]

@leiicamundi Let me know when this PR is ready for a TW review 👍

[Langleu]

@leiicamundi could you rebase the branch, so your change is isolated to what you wanted to restructure.

[leiicamundi]

@Langleu I'll do it today

[leiicamundi]

Hey @mesellings, @Langleu, this PR is now rebased onto main and ready to be reviewed :)

[mesellings]

Thanks @leiicamundi I'll do this for you now 👍

[mesellings]

@leiicamundi I have reviewed and made commits directly to the branch for readability, writing standards (for example, we do not use "e.g.", but rather "for example,", and general grammar.

Great work - happy to approve 👍

[Langleu]

Overall, cool suggestion.
Not the biggest fan of the detail column as it doesn't align well on the wording. Also some rows are just repeating the same information or completely out of context.

[leiicamundi]

Hello @Langleu, thanks for your review. I've modified the identified parts, let me know what you think about the changes.

cc @theburi if you want to do other changes on this doc, feel free to use this PR if you want (I'll not update it anymore today and it will be easier to deal with potential conflicts with #4278)

[Langleu]

thanks for the quick changes 🙇.
Looks good from my side 🚀

[github-actions]

🧹 Preview environment for this PR has been torn down.