8.9 unified configuration mapping

[mesellings]

Description

Addresses the need to inform users of the new properties and any mappings involved with the move to a unified configuration for the Orchestration Cluster in 8.9.

Closes #7510.

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 Documentation 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

• The commit history of this PR is cleaned up, using {type}(scope): {description} commit message(s)

• My changes are for an upcoming minor release and are in the /docs directory (version 8.9).
• 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, @mesellings! 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.8/.

• docs/self-managed/components/orchestration-cluster/core-settings/configuration/partials/_api.md
• docs/self-managed/components/orchestration-cluster/core-settings/configuration/partials/_cluster.md
• docs/self-managed/components/orchestration-cluster/core-settings/configuration/partials/_licensing.md
• docs/self-managed/components/orchestration-cluster/core-settings/configuration/partials/_monitoring.md
• docs/self-managed/components/orchestration-cluster/core-settings/configuration/partials/_processing.md
• docs/self-managed/components/orchestration-cluster/core-settings/configuration/partials/_security.md
• docs/self-managed/components/orchestration-cluster/core-settings/configuration/partials/_system.md
• docs/self-managed/components/orchestration-cluster/core-settings/configuration/properties.md
• docs/self-managed/react-components/_config-table.js

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]

@mesellings just need to update the properties for all the data sections before moving onto the Helm Charts.

@buccarel I have now completed the following:

• Added in all 8.9 properties from the sheet to the properties update page.
• Added the new properties to the property reference page except for the data ones which I will do next.

Then it will just be validation and adding Helm Chart values to the property reference page.

One other thing I noticed is there are a few discrepencies between the default values in the spreadsheet and the Javadoc I am using for descriptions (i.e. https://github.com/camunda/camunda/blob/updated-8.9.0-alpha3/configuration/src/main/java/io/camunda/configuration/Actor.java) - if I have to choose, which default value should I use?

[github-actions]

🧹 Preview environment for this PR has been torn down.

[mesellings]

@buccarel @RomanJRW I've merged this PR to get the changes in and avoid any conflicts as it is a large PR.

Summary:

• This PR updates the changed properties for 8.9 page with all the 8.9 changed properties marked as completed in the spreadsheet.
• Additionally, I began the task of adding all the new properties into the 8.9 properties page, but noticed @EuroLew is making updates here, hence merging now rather than later to make it easier to collaborate.
• My next task is to update the data sections on this page, for example like @EuroLew has been doing with the secondary storage section. I will do this in a follow-up PR.
• The final task will be to update all the properties to have Helm Chart entries - what is the best/easiest/fastest way of getting this info do you think @buccarel?
• If I have time, I will go through this whole config section and give it a TW review etc to tidy everything up as well.