Fix flaky shouldNotifyCommitListener test

[deepthidevaki]

Description

Use commitIndex to verify that listener is notified instead of using called count. It is possible that one of the follower committed the InitialEntry after the CommitListener is added. As a result the test failed because the expected call count is different.

Related issues

closes #9372

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.

[github-actions]

Unit Test Results

   777 files  ±  0     777 suites  ±0   1h 34m 50s ⏱️ + 2m 10s
5 625 tests +18  5 618 ✔️ +18  7 💤 ±0  0 ❌ ±0 
5 795 runs  +18  5 788 ✔️ +18  7 💤 ±0  0 ❌ ±0 

Results for commit 602bab6. ± Comparison against base commit ff1b36f.

[Zelldon]

Thanks 👍

bors r+

[ghost]

Build succeeded:

• Go linting
• Test summary
• Java checks

[backport-action]

Successfully created backport PR #9524 for stable/8.0.