adjust performance numbers based on new benchmark results

[hisImminence]

Description

This PR updates the performance numbers based on the new results of the benchmarks (see slack message from @rodrigo-lourenco-lopes ).

These values are just valid for 8.6+.

• Assigning @rodrigo-lourenco-lopes to double check the numbers.
• Assigning @mesellings as you had been responsible for the docs in the first place as a FYI and to make sure I dont change anything unexpected :D

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 (--> just valid for 8.6).
• 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.

[mesellings]

I think the comma numeric separator should be changed possibly, other than that it looks good from a writing standpoint 👍

[rodrigo-lourenco-lopes]

Thanks for the changes! 🚀

[mesellings]

Lgtm 👍 🚀

[mesellings]

@akeller I'll do a docs release to get this out 👍

[github-actions]

🧹 Preview environment for this PR has been torn down.