chore(deps): bump zeebe-bom from 1.0.1 to 1.1.0

[dependabot]

Bumps zeebe-bom from 1.0.1 to 1.1.0.

Release notes

Sourced from zeebe-bom's releases.

Zeebe 1.1.0-alpha1

Release: 1.1.0-alpha1

Enhancements

Broker

• Detect segment descriptor field corruption (#7041)

Go Client

• Split address and port in zbctl (#3104)

Bug Fixes

Broker

• Segment descriptor is loaded twice (#7116)
• MaxAppendBatchSize configuration printed out at broker startup up shows incorrect value (#7048)
• Back to back role changes cause ZeebePartition to go unhealthy and transition to inactive (#6997)
• The advertised address should be unresolved locally in the broker (#6983)
• Broker crashes if there is an empty log segment (#6979)
• The event scope of a timer start event is not removed when already triggered (#6976)
• A call activity can't be completed or terminated (#6959)
• The temporary variables are not removed on termination (#6958)
• The event scope of a timer start event is not removed (#6955)
• I can't resolve an incident caused by the input collection for a sequential multi-instance (#6952)
• Partition incorrectly marked as unhealthy when broker is closing. (#6938)
• Multi-instance variables are wrong after resolving an incident (#6933)
• Variables are overridden when the subprocess is completed (#6926)
• Memory leak in NettyMessagingService (#6878)
• Unable to resolve incident for multi instance output element expression failure (#6546)
• Redeploying process model with Timer start event causes retriggering (#6515)
• The source record position may point to a wrong record (#5420)
• ElasticExporter export metrics for bulk even when bulk is not flushed successfully (#4830)

Go Client

• [zbctl] unable to publish message containing space in message name (#6596)
• Diff in zbctl test output is incorrect (#6967)

Misc

• Zeebe-broker-1 and zeebe-broker-2 will remind "warn" every five minutes io.camunda.zeebe.snapshots.impl.FileBasedTransientSnapshot - Failed to delete pending snapshot" (#7098)
• NPE in StandaloneGateway (#7018)
• IOException: No space left on device (#6505)

Documentation

• Some env variables are mentioned wrong in configuration template (#6325)

Merged Pull Requests

• Adds new issues to the Zeebe project in "Awaiting triage" status (#7125)

Commits

• 8a53626 [maven-release-plugin] prepare release 1.1.0
• 63ca4a5 chore(project): update go embedded version data
• 377c9a8 merge: #7415
• 83b4bd7 merge: #7423
• 3e0a512 test(broker): add test for raft config
• 12f626a doc(config): add raft request timeout to config templates
• e457689 feat(broker): add configuration for raft request timeout
• c6ebd07 build(test): ignore configuration from api check
• 9bc3ab3 feat(raft): make requestTimeout configurable
• 02b83e6 build(parent): set offline dependency to scope test
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)