Update docs about sdk client configuration options

[eppdot]

Description

closes 26700

Synced the spring sdk configuration docs with the actual property classes in code.

In general I just added the missing properties and re-organized a bit the structure.

There are a few open TODOs, that we need to check

• Max metadata size: Needs better explanation
• Deployment enabled: Didn't find any usage in the project, thus outdated?
• Copy docs to older versions

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.

[nicpuppa]

A custom maxMetadataSize allows the client to receive larger or smaller response headers from Camunda.

[nicpuppa]

It seems not used, so we can remove it

[eppdot]

@nicpuppa I added your suggestions and copied the updates to the 8.6 folder. I guess the PR is then ready to go or do you think something is missing? I would also like to learn how to merge & deploy, thus should we do that together on moday?

[akeller]

@nicpuppa I added your suggestions and copied the updates to the 8.6 folder. I guess the PR is then ready to go or do you think something is missing? I would also like to learn how to merge & deploy, thus should we do that together on moday?

Hi @eppdot, I added the tech writers group to review your PR. We usually handle the merge and deploy based on how you respond to the PR template.

[nicpuppa]

LGTM 🚀 👏

[mesellings]

@eppdot Approved, great work, just a few rewording suggestions/typos. but non-blocking 👍 🚀

[eppdot]

@mesellings Thanks a lot for reviewing 🚀 I just took over all your suggestions.

As is this my first PR here, can you explain to me what the next steps are?

Cheers, Stephan

[mesellings]

Approved - nice job! 🚀

[mesellings]

@eppdot Hi, great job for your first docs PR!

• Once you are happy for this to be released to the docs site, either you (or we) can merge it into the docs codebase.
• It will then be released in either the next docs patch release, or we can release it asap if it need to be live quicker than that, or to an agreed timeframe - looking at the description, this should be released quickly, so I can merge it in and release the docs if you like?

Tip: Use the Description check boxes and labels to let us know when it needs to be released, to save us having to ask you - makes it easier for everyone to see when the PR needs to go out, and if it belongs to a release.

[mesellings]

@eppdot I will be doing a docs release today/tomorrow, so I merged it for you, and it will get included in this release 👍

[github-actions]

🧹 Preview environment for this PR has been torn down.