batch1_2024: changing berachain to not honor the finality tag due to … (

#1522)

…possible re-orgs at depth 1

Despite berachain support finality tag they seem to have re-orgs with
block depth 1, so we will rely in the finality depth of 10 which should
be working all the times.

full thread:
https://chainlink-core.slack.com/archives/C03ANJB9VB7/p1730998603539279


## Motivation


## Solution

core/chains/evm/config/toml/defaults/Berachain_Testnet.toml

@@ -7,9 +7,6 @@ LogPollInterval = '10s'
 # finality_depth * block_time / 60 secs = ~0.8  min (finality time)
 NoNewFinalizedHeadsThreshold = '5m'
 
-
-FinalityTagEnabled = true
-
 [GasEstimator]
 EIP1559DynamicFees = true
 Mode = 'FeeHistory'

docs/CONFIG.md

@@ -8565,7 +8565,7 @@ AutoCreateKey = true
 BlockBackfillDepth = 10
 BlockBackfillSkip = false
 FinalityDepth = 10
-FinalityTagEnabled = true
+FinalityTagEnabled = false
 LogBackfillBatchSize = 1000
 LogPollInterval = '10s'
 LogKeepBlocksDepth = 100000