feat: update l2 erc20 bridge address in updater as well (#3500)

## What ❔

update l2 erc20 bridge address as well as l2 shared bridge

## 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 `zkstack dev fmt` and `zkstack dev
lint`.

Co-authored-by: Jobe Smith <[email protected]>

Author: perekopskiy

core/node/api_server/src/web3/state.rs

@@ -241,8 +241,9 @@ impl BridgeAddressesHandle {
         self.0.write().await.l1_shared_default_bridge = Some(l1_shared_bridge);
     }
 
-    pub async fn update_l2_shared_bridge(&self, l2_shared_bridge: Address) {
+    pub async fn update_l2_bridges(&self, l2_shared_bridge: Address) {
         self.0.write().await.l2_shared_default_bridge = Some(l2_shared_bridge);
+        self.0.write().await.l2_erc20_default_bridge = Some(l2_shared_bridge);
     }
 
     pub async fn read(&self) -> api::BridgeAddresses {

core/node/node_framework/src/implementations/layers/web3_api/server/bridge_addresses.rs

@@ -80,7 +80,7 @@ impl L1UpdaterInner {
                 // - To not undo the previous change in case of a network error
                 if info.should_use_l2_asset_router {
                     self.bridge_address_updater
-                        .update_l2_shared_bridge(L2_ASSET_ROUTER_ADDRESS)
+                        .update_l2_bridges(L2_ASSET_ROUTER_ADDRESS)
                         .await;
                 }
             }