Bumps [mixme](https://github.com/adaltas/node-mixme) from 0.5.1 to 0.5.2.
- [Release notes](https://github.com/adaltas/node-mixme/releases)
- [Changelog](https://github.com/adaltas/node-mixme/blob/master/CHANGELOG.md)
- [Commits](adaltas/node-mixme@v0.5.1...v0.5.2)

---
updated-dependencies:
- dependency-name: mixme
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

…rn/mixme-0.5.2

chore(deps): bump mixme from 0.5.1 to 0.5.2

Adds new config options to the watcher to allow it to upgrade in
a non breaking way. New config options include setting a global
`pollForPending` and `blocksToFetch`. It is also possible to
specify the number of blocks to fetch on each `Layer`.

The event ids are precomputed and held as globals instead of computed
on the fly each time.

…ocksToFetch

Watcher: l1 vs l2 blocksToFetch

docs: point to new specs repository

…uebatch

batch-submitter: remove call to `appendQueueBatch`

[added] coverage for getMerkleTreeProof

…ate-dump-process

Remove L1 contracts from L2 state dump process

Allow the DTL to sync from multiple web3 backends using
the `ethers.providers.FallbackProvider`. Multiple URLs
can be passed through as a comma delimited string to
configure multiple providers.

A helper function is added to `core-utils` to allow
easy configuration between services. This PR only introduces
the usage of the fallback provider into the DTL. In the
future, it should be added to other services that query L1
as well.

feat: use FallbackProvider in the DTL

Fix `toExecutionManagerRun` in cases where `asOvmMessage` isn't applied.
Note that tracing currently does not work for optimistic ethereum.

l2geth: to execution manager run

fix: update contracts release to patch