Improve EE901: Unexpected case. Contract name does not exist in interface mapping.

[DZakh]

Describe the bug

I've seen a few cases where users get the error when they register a contract defined in the global contracts config but are not connected to the network.

Also, the error message is not helpful at all. But I think we can do better and automatically connect global contracts without the need to define them in the network config.

To fix it

To Reproduce

1. Add a global contract in the config.yaml
2. Register the contract dynamically via a contract factory
3. Expect it to work, but get the weird error.

Expected behavior

Expect it to register the contract.

Hosted Service (please complete the following information):

• Envio version: 2.9.1

[ethsdev]

Hi, @DZakh , sorry for leaving comment here without your agreement and respecting the team rule. Because I wanna contribute to Envio team's development and join your team, so I am going to solve issues. So could you give me some issue to be solved quickly as test task?

[DenhamPreen]

hey @solthereum, no worries on leaving a comment here although once you've read this we will likely delete this convo. Feel free to join our discord and let us know what you would like to get involved on more specifically :)