Update camunda REST API doc

[camunda-docs-pr-automation]

Description

This is an autogenerated PR by the sync api specs workflow.
This PR contains every changes made to the REST api specs in the monorepo in the last week.
This PR contains also all the generated OpenAPI files related to the changes.

When should this change go live?

• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for the next minor and are in /docs directory (aka /next/).
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[github-actions]

👋 🤖 🤔 Hello, @camunda-docs-pr-automation[bot]! 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/apis-tools/orchestration-cluster-api-rest/specifications/modify-process-instance.api.mdx
• docs/apis-tools/orchestration-cluster-api-rest/specifications/search-user-task-audit-logs.api.mdx
• docs/apis-tools/orchestration-cluster-api-rest/specifications/sidebar.ts

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]

Skim approval

[github-actions]

🧹 Preview environment for this PR has been torn down.

[afgambin]

@mesellings I declined this change in a previous automatic PR because I believe it does not follow our sentence case style. See, for instance, “Decision definition” or “Decision instance” in the same section of the left navigation bar.

I’m wondering why, in this case, the auto PR is triggering this change - all of these section headings seem to be defined in the same way in the related sidebar.ts file (/apis-tools/orchestration-cluster-api-rest/specifications/sidebar.ts), using the "category" type.

[mesellings]

Ah good spot @afgambin - I tend to skim approve these so we don't block the updates, but historically we don't have time to check the API reference docs in the team - let's chat to Tobias and the team at the kickoff and see how we can best tackle this now? It's not ideal, but as the API reference docs exist and are 'good enough', they were one of the things we first dropped priority-wise. I'll also add this as a theme for us to look at as a team.

[afgambin]

sgtm, thank you!