added scope to properties

[jonathanlukas]

Description

This property can be configured, but is undocumented:

https://github.com/camunda/camunda/blob/main/clients/spring-boot-starter-camunda-sdk/src/main/java/io/camunda/zeebe/spring/client/properties/common/ApiProperties.java#L24

When should this change go live?

• 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]

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

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

[akeller]

Checking in with the team to see if this will also be available in 8.5 as mentioned via camunda/camunda#23072

[akeller]

Duplicate of #4393, however they haven't backported that PR.

[jonathanlukas]

@akeller well, one of them has to be merged. A customer is missing it.

btw this is required for ms entra integration.

[jonathanlukas]

I just filed a PR so that the old place where the scope was added points to the new one: camunda/camunda#23673

Btw the old property is zeebe.client.cloud.scope

[megglos]

This is not released in 8.5 see the original issue camunda/camunda#23071 . It will be included in the next 8.5 patch.

We need to revert this.

Please always refer to the actual originating issue for context.

Thanks @akeller for the ping.