6671 adjust properties for identity initialization

[Ben-Sheppard]

Description

Closes #6671

This PR updates the overview page for Orchestration Identity focusing on renaming the existing Helm tab to be application.yaml and adding a helm tab where necessary.

Additionally I spotted some inconsistencies in the property reference recently change too so included a cleanup here.

As per the linked issue, I looked for additional places but couldn't immediately spot any relevant configuration for the new architecture where the config is and didn't want to block this PR because of that. If there are additional places I will follow up with them.

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.8).
• 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]

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

[ThorbenLindhauer]

Thanks for preparing, please see my detailed comments.

In addition, on the initialization page please also add a Helm tab to the example for the default user configuration.

[ThorbenLindhauer]

Suggested change

	| `orchestration.security.authentication.oidc.audiences` | Comma-separated list of audiences to validate in the OIDC token. | |
	| `orchestration.security.authentication.oidc.audience` | Comma-separated list of audiences to validate in the OIDC token. | |

See https://github.com/camunda/camunda-platform-helm/blob/de19d5e1f609a3ed615b5507817581c01f4f86a8/charts/camunda-platform-8.8/templates/orchestration/files/_application-unified.yaml#L102

And I believe that takes a single value (might be wrong though). See also the Helm value orchestration.security.authentication.oidc.backwardsCompatibleAudiences that we could mention here.

[Ben-Sheppard]

I decided to not document this property here, its a property that is automatically set by the helm charts when required and I'm not sure its inclusion here adds much value in typical operation

[ThorbenLindhauer]

It's part of the migration guide here: https://docs.camunda.io/docs/next/self-managed/deployment/helm/upgrade/upgrade-hc-870-880/#values-key-changes

Anyway, I don't mind too much not documenting it, you can decide.

[christinaausley]

@Ben-Sheppard Just let me know when you are ready for final review 👍

[ThorbenLindhauer]

Thanks, looks good to me.

Re the one open discussion, feel free to decide in either direction.

[ThorbenLindhauer]

Ah, and one more comment: Now that the 8.8 docs are released, this needs a "backport" into the 8.8 directory.

[Ben-Sheppard]

Thank you @ThorbenLindhauer - the changes are already applied to the 8.8 docs 👍🏻

This is ready for a final review @christinaausley :)