feat: Improve proving networks setup (#4563)

## What ❔

* Add `attempts` column for submitting validation results. Initially the
setup worked the way that validation results are being sent with
retries, but without any measuring of attempts - so they are being sent
until accepted. In some cases it gets the system stuck - like change of
contracts or some other issues. So this PR adds `attempts` and metrics
for reached max attempts(configurable) - for which we can configure
alert and react.
* Metrics `proven_batches` and `acknowledged_batches` were reworked, so
they emit the latest proven/acknowledged batch instead of total amount.
* `failed_to_send_txs` metric was removed in favor of
`reached_max_attempts` metric.
* New metrics added:
- `submitter_address` - to track the address of the submitter in
Grafana, for easier accesibility
    - `submitter_balance` - to track/set alerts on balance of submitter
- `contract_address` - address of proof manager contract - to be able to
track the contract's state from Grafana
* Crypto dependencies bumped - fixes the issue with verifier panicking
if receiving wrong proof. We don't want to crash the component in case
the submitted proof was incorrect
* Add filtering events by chain ID of current network - so we won't
receive proofs/events from other networks.

## Why ❔

This PR improves a few things in proving networks setup as preparation
to going in production.

## Is this a breaking change?
- [ ] Yes
- [ ] No

## Operational changes
<!-- Any config changes? Any new flags? Any changes to any scripts? -->
<!-- Please add anything that non-Matter Labs entities running their own
ZK Chain may need to know -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zkstack dev fmt` and `zkstack dev
lint`.

Author: Artemka374

core/Cargo.lock

@@ -251,22 +251,22 @@ rust-eigenda-signers = "0.1.6"
 # However, for the historical version of protocol crates, we have lax requirements. Otherwise,
 # Bumping a crypto dependency like `boojum` would require us to republish all the historical packages.
 
-circuit_encodings = "=0.153.3"
-circuit_sequencer_api = "=0.153.3"
-circuit_definitions = "=0.153.3"
-crypto_codegen = { package = "zksync_solidity_vk_codegen", version = "=0.32.5" }
+circuit_encodings = "=0.153.4"
+circuit_sequencer_api = "=0.153.4"
+circuit_definitions = "=0.153.4"
+crypto_codegen = { package = "zksync_solidity_vk_codegen", version = "=0.32.6" }
 
-kzg = { package = "zksync_kzg", version = "=0.153.3" }
+kzg = { package = "zksync_kzg", version = "=0.153.4" }
 
 zk_evm_1_3_1 = { package = "zk_evm", version = "0.131.0-rc.2" }
 zk_evm_1_3_3 = { package = "zk_evm", version = "0.133" }
 zk_evm_1_4_0 = { package = "zk_evm", version = "0.140" }
 zk_evm_1_4_1 = { package = "zk_evm", version = "0.141" }
 zk_evm_1_5_0 = { package = "zk_evm", version = "=0.151.8" }
-zk_evm_1_5_2 = { package = "zk_evm", version = "=0.153.3" }
+zk_evm_1_5_2 = { package = "zk_evm", version = "=0.153.4" }
 
-fflonk = "=0.32.5"
-bellman = { package = "zksync_bellman", version = "=0.32.5" }
+fflonk = "=0.32.6"
+bellman = { package = "zksync_bellman", version = "=0.32.6" }
 
 # New VM
 zksync_vm2 = "=0.5.0"