If IMA was upgraded on SKALE chain connectSchain function works incorrectly

[DimaStebaev]

TokenManagerLinker has a function connectSchain that setup interaction between token managers and message proxies.
For each registered token manager it sets address of receiver of it's message. Now it's assumed that all token managers are predeployed and have the same addresses. But this invariant is violated after IMA upgrade.

For example recently TokenManagerERC721WithMetadata was introduced and it has different address on brand new SKALE chains and on upgraded ones what means that if a new chain is connected to old one or vice versa the token managers is not properly connected.

To Reproduce
Steps to reproduce the behavior:

1. Start SKALE chain with old version of IMA
2. Start SKALE chain with new version of IMA
3. Update IMA on the first chain
4. Call a connectSchain function of TokenManagerLinker to connect two chains

Expected behavior
ERC721WithMetadata can be transferred between chains

Additional context
The problem will be relevant for all new token managers or IMA instances that will not be predeployed.