BCFR-144 enforce repeatable read

[dhaidashenko]

EnforceRepeatableRead = true guarantees that MultiNode will not route requests to an RPC that laggs on the latest finalized block.

FinalizedBlockOffset was increased on chains with mean finalized block time <= 30s to gracefully handle cases when RPCs constantly lag behind on the latest finalized block.

[github-actions]

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
6 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[prashantkumar1982]

Asked a separate question about whether we have enough metrics to alarm us when all RPCs go out of sync due to lagging on Finality.
But this change overall is good.

[prashantkumar1982]

Asked a separate question about whether we have enough metrics to alarm us when all RPCs go out of sync due to lagging on Finality. But this change overall is good.

From @dhaidashenko : If on new request there is no healthy RPC we'll log a critical error. It does not contain actual reason, but it could be used as a signal for deeper investigation.
We also periodically report all RPCs states (both via logging and prometheus), where we'll explicitly see if RPC is in FinalizedBlockOutOfSync state.