fix: Concurrent demote and write txns

[as51340]

Protect concurrent demote and write txns during the execution.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[as51340]

Tracking

• [Link to Epic/Issue]

Standard development

• Update unit/E2E tests
• Compare the benchmarking results between the master branch this branch

CI Testing Labels

• Select the appropriate CI test labels (CI -build=build-name -test=test-suite)

Documentation checklist

• Add the documentation label
• Add the bug / feature label
• Add the milestone for which this feature is intended
  • If not known, set for a later milestone
• Write a release note, including added/changed clauses
  • If the main received a request for demotion while it was executing a write txn, it could've resulted in an issue if GIDs of the latest txn from the new main overlap with the GIDs from the currently running write txn on the main. Until this PR, concurrent demotion and write txns were running safely concurrently but only if the write txn came to the commit phase. Execution part wasn't protected. In order to demote the instance, we will now wait for all write transactions to finish. Users can now expect smooth demotion of the main instance, even in the case of a long-running write transaction. #3594
  • What has changed? What does it mean for a user? What should a user do with it? [#{{PR_number}}]({{link to the PR}})
• [ Documentation PR link memgraph/documentation#XXXX ]
  • Is back linked to this development PR