fix: return int for process version incident alert

[RomanJRW]

Description

To be merged with the alpha release in January.

In this PR, we are fixing a regression in the type and content of the process version field. We will also introduce a new version tag field so that this property is still available to customers.

This is the corresponding doc change for that PR.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
• This is already available but undocumented and should be released within a week. (add available & undocumented label)
• This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
• This is part of a scheduled alpha or minor. (add alpha or minor label)
• There is no urgency with this change (add low prio label)

PR Checklist

• The commit history of this PR is cleaned up, using {type}(scope): {description} commit message(s)

• My changes are for an upcoming minor release and are in the /docs directory (version 8.9).
• My changes are for an already released minor and are in a /versioned_docs directory.

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[mesellings]

@RomanJRW I've added some more detail to the announcement and moved it into the breaking changes section - please check for technical accuracy etc - also, I added a caution to the webhook alerts page itself, but we can remove if you think that is too much? Otherwise, lgtm for a first iteration 🚀

[mesellings]

Re-approved after slight rewording

[mesellings]

@fyi @afgambin this can be merged in January as part of the alpha release, but not until then (waiting for the patch fix)

[RomanJRW]

@mesellings - the changes are now merged and will be included in the 8.8.9 release. Documentation is good to go from my perspective around the same time as the release announcements

[RomanJRW]

@mesellings - nudging here, should this now be merged?

[mesellings]

Thanks for the nudge @RomanJRW - yes I think we can merge this as long as you are happy the changes will be visible before the release on Tuesday? Or we can wait until closer still (e.g. Monday) - we monitor the open PRs so it won't be forgotten if we hold off?

[RomanJRW]

All good for me, thanks for merging 👍

[github-actions]

🧹 Preview environment for this PR has been torn down.