Resolve flaky shouldTriggerTimerTest

[remcowesterhoud]

Description

This test was flaky because the margin of the between was too tight. The CI isn't always fast enough to ensure the timer gets triggered between 100-150ms.

Since we don't really like timers of 100ms we changed to a more realistic scenario with a timer of 1 minute. We also increased the margin to have an extra minute to prevent flakyness

Related issues

closes #10978

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.)
• 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]

@remcowesterhoud 👍

bors merge

[github-actions]

Test Results

   957 files  ±  0     957 suites  ±0   1h 41m 39s ⏱️ - 1m 37s
7 625 tests  - 66  7 618 ✔️  - 66  7 💤 ±0  0 ❌ ±0 
7 825 runs   - 66  7 816 ✔️  - 66  9 💤 ±0  0 ❌ ±0 

Results for commit 756fd46. ± Comparison against base commit 929988c.

[zeebe-bors-camunda]

Build succeeded:

• Test summary

[backport-action]

Successfully created backport PR #11035 for stable/8.0.

[backport-action]

Successfully created backport PR #11036 for stable/8.1.