Added config options to control HeadTracker's support of finality tags

[dhaidashenko]

• Disabled by default HeadTracker's support of finality tags
• Added config option, that allows to abort HeadTracker's backfill if gap between the current head and latest finalized block is too large.
• Enabled HeadTracker's support of finality tags for chains that are a testnet and max observed finality gap is less than 2000 blocks (query used to validate chain)

[dimriou]

Shouldn't the default value be false otherwise every chain will override finality tag by default? AFAIK the only chain that needs this as true is Arbitrum

[dhaidashenko]

IMHO safer approach is to disable it for all of the chains and only enable it for those that we've seen behave normally. After the optimisation we will enable it for all chains.

[dimriou]

I might be a bit confused here, but don't we want to enable Finality Tag on all chains they support it and if they show they have issues, then disable it by setting FinalityTagBypass = true ? Most chains don't have more than 10k finality depth. Otherwise we would have to explicitly test every chain we are operating on. I mean I'm ok either way, but we need to make sure Finality Tag is enabled on every chain we can. Same thing happened with dynamic transactions. They are still disabled in many chains because no one ever did the switch.

[cl-sonarqube-production]

Quality Gate passed

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