Fix expectations in lock manager test

[hubertp]

Pull Request Description

The test optimistically assumed that threads will mostly execute in order, while ignoring all other possibilities.
Changes the order of the report so that we remove the potential non-determinism.

As discovered in https://github.com/enso-org/enso/actions/runs/8516468592/job/23325541262?pr=9584#step:8:1530

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• All code follows the
  Scala,
  Java,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• All code has been tested:
  • Unit tests have been written where possible.

[hubertp]

Adding @radeusgd in /cc as you wrote the library/tests

[radeusgd]

Thanks for fixing the test

[radeusgd]

The test optimistically assumed that threads will mostly execute in order, while ignoring all other possibilities.

I'd just like to correct that I was not 'optimistically' assuming the ordering - the whole purpose of TestSynchronizer was to ensure correct ordering of events. It was just an oversight that the order of report and signal was mixed up - I must have indeed wrongly assumed that these 2 operations will mostly execute atomically, but obviously they weren't, so report always must come before corresponding signal to avoid unexpected paths.