Implement a job backoff timeout on Zeebe Java client side

[aivinog1]

Description

I implemented the usage of the backoff parameter in the Zeebe Java Client and @saig0 fixed the problem with flushing responses.

Related issues

#5629

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

• The changes are backwards compatibility with previous versions
• If it fixes a bug then PRs are created to backport the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. backport stable/1.3) to the PR, in case that fails you need to create backports manually.

Testing:

• There are unit/integration tests that verify all acceptance criterias of the issue
• New tests are written to ensure backwards compatibility with further versions
• The behavior is tested manually
• The change has been verified by a QA run
• The impact of the changes is verified by a benchmark

Documentation:

• The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
• New content is added to the release announcement
• If the PR changes how BPMN processes are validated (e.g. support new BPMN element) then the Camunda modeling team should be informed to adjust the BPMN linting.

Please refer to our review guidelines.

[saig0]

@aivinog1 thank you for your contribution 🎉
Looks all very well 👍

This enables a really cool feature. I'm looking forward to see it in action 🚀

[saig0]

bors merge

[zeebe-bors-camunda]

Build succeeded:

• continuous-integration/jenkins/branch
• Smoke tests on macos-latest
• Smoke tests on windows-latest
• Smoke tests on ubuntu-latest