[ENHANCEMENT] mapping rule proconfigured using EntraID/OIDC

[Szik]

Describe the use case:
provide values in values.yaml for installation of C8 SM using EntraID can be used for configuring mapping rules in core/orchestration cluster

Describe the enhancement/feature:
currently, mapping rule for e.g. Connectors hardcoded yet copnnectors fully configured with what is provided by user/customer
client_id and value
also thinkable: the client "demo" used via keycloak equals the initial claim name and value provided using EntraID and add this one to the admin role

Desired outcome and acceptance tests:

• connectors client added as mapping rule
• initial claim name and value are used for admin user in OC

[hamza-m-masood]

Please check this message: https://camunda.slack.com/archives/C07UA4C7STY/p1758297439923189

There is no need to mention predefined user and client mappings on the values.yaml. This really simplifies the OIDC setup needed for the orchestration cluster through the values.yaml.

The connectors client is now dynamic with no hardcoded mapping

[hamza-m-masood]

I will close this issue since connectors client does not have a hardcoded mapping anymore.