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

[dependabot]

Bumps zeebe-bom from 1.0.1 to 1.1.1.

Release notes

Sourced from zeebe-bom's releases.

Zeebe 1.1.0

Release: 1.1.0

Blog Post: https://camunda.com/blog/2021/07/camunda-cloud-110-released/

Enhancements

Broker

• Allow to configure raft electionTimeout and heartbeatInterval (#7393)
• Distribute leaders uniformly in the cluster in a best-effort way (#7258)
• Detect segment descriptor field corruption (#7041)
• Configure raft timeouts and failure detection parameters (#6320)
• I can retry a job if an error was thrown but not caught (#6000)

Go Client

• Split address and port in zbctl (#3104)

Misc

• Adjust Camunda Cloud client builder to new domain names (#7391)
• A user can deploy a process definition with a business rule task (#7157)
• A user can deploy a process definition with a send task (#7156)
• A user can deploy a process definition with a script task (#7155)

Bug Fixes

Broker

• Race condition in messaging service causes "infinitely" waiting requests (#7360)
• Unnecessary VariableRecord.UPDATED if the variable exists and its value has not changed (#7295)
• Snapshottting process is stuck and no new snapshot are taken (#7207)
• Resolving an uncaught error incident does not lead to new incident (#7160)
• Follower doesn't start with corrupted snapshot (#7136)
• correlation key validation for message boundary event is missing in specific case (#7131)
• A rejected incident resolve command was simultaneously accepted (#7127)
• Segment descriptor is loaded twice (#7116)
• Failing to process boundary event on embedded sub process on event sub process (#7097)
• 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)
• Kafka cannot be loaded through our ExporterJarClassLoader (#4196)

Gateway

• Race condition in messaging service causes "infinitely" waiting requests (#7360)

... (truncated)

Commits

• de3ca35 [maven-release-plugin] prepare release 1.1.1
• f4d077b chore(project): update go embedded version data
• a5fc0ae fix(ci): update release job to use different github-release artifact
• 4c4f904 merge: #7527
• 23810f1 fix(ci): allow zbctl errors in qa testbench
• 60e2501 merge: #7517
• beaba6d test(engine): remove outdated test cases
• 0ab9aaa merge: #7493
• 05d73ae refactor(ci): change latest stable branch and schedule for QA run
• e37cd5a merge: #7467
• 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)