Necessary monitoring for both l1 and mev-commit chain contracts

[shaspitz]

We have a monitoring/alerts system setup for components like the oracle. There is more necessary slack alerts w.r.t contract state that'll be necessary prior to mainnet:

• All slash events (provider slashes, and validator slashes) should invoke an alert
• Any failed validator slash (w.r.t oracle) should invoke an alert
• Each vault collateral's stakeAmount in MevCommitMiddleware, must correspond roughly to some global eth amount. ie if a vault's ERC20 price deviates significantly from 1-3 ETH, our team needs to set a new slashAmount. Therefore we need to monitor the price of each vault's ERC20.
• The bridge relayer should have at least 1 ETH on both L1 and the mev-commit chain at any given time.
• Related, each bridge gateway's finalizationFee must be set higher than finalization tx cost for that chain. We need to monitor the diff between finalzationFee and actual tx cost. If the diff is too large, our team would be required to change the finalizationFees on-chain.
• Any TransferNeedsWithdrawal events from fix: malicious user can dos bridge transfer finalization  #448 should invoke an alert
• More related to contracts?