fix(zk_toolbox): Use the same l2 address for shared and erc20 bridge (#…

…2260)

## What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## 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 `zk fmt` and `zk lint`.
- [ ] Spellcheck has been run via `zk spellcheck`.

Signed-off-by: Danil <[email protected]>

zk_toolbox/crates/zk_inception/src/config_manipulations.rs

@@ -79,6 +79,8 @@ pub fn update_l2_shared_bridge(
     let mut contracts_config = ContractsConfig::read_with_base_path(shell, &config.configs)?;
     contracts_config.bridges.shared.l2_address =
         Some(initialize_bridges_output.l2_shared_bridge_proxy);
+    contracts_config.bridges.erc20.l2_address =
+        Some(initialize_bridges_output.l2_shared_bridge_proxy);
     contracts_config.save_with_base_path(shell, &config.configs)?;
     Ok(())
 }