feat(protocol): Fix new token migration change

[adaki2004]

Current scenario:

1. Canonical token X lives on L1.
2. No bridged counterpart is bridged to L2 - yet. (Hence noone bridged token X just yet.)
3. We decide to pre-deploy a native X on L2 and we call the changeBridgedToken() in ERC20Vault afterwards.
4. It would call (wrongly) the IBridgedERC20(btokenNew).changeMigrationStatus(address(0), false); but in BridgedERC20Base.sol , this check would revert - because inbound is false, and migratingAddress is address(0) (exactly how we call that BridgedERC20Base..)

        if (addr == migratingAddress && inbound == migratingInbound) {
            revert BB_INVALID_PARAMS();
        }

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
bridge-ui-v2-a5	✅ Ready (Inspect)	Visit Preview	Jan 9, 2024 1:21pm
bridge-ui-v2-a6	✅ Ready (Inspect)	Visit Preview	Jan 9, 2024 1:21pm
bridge-ui-v2-internal	✅ Ready (Inspect)	Visit Preview	Jan 9, 2024 1:21pm