Improve the failover process in HA when using multitenancy

[as51340]

The failover in the MT code now has a different logic. We 1st try to find the instance which has most newest databases. If there are multiple instances that are newest on the same number of databases, the sum of timestamps of all databases decides. The instance which has larger sum it is assumed to be newer.

[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
  • There is now an improved logic for selecting the new MAIN instance during the failover in the MT environment. Instance which has most newest databases is considered the newest. Users will now have a smaller chance of experiencing the loss of committed data. #2812,
• Documentation PR link memgraph/documentation
  • Is back linked to this development PR
• [ Tag someone from docs team ] @katarinasupe

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
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