Map serialized EVM address to associated types

[sisyphusSmiling]

Issue To Be Solved

This issue arose when creating batch onboarding transactions. That is, the current EVM address onboarding check validates one of two things:

• Is the EVM contract address factory-deployed?
• Is there a Cadence contract with the appropriately derived name deployed in the bridge account?

If either of those things are true, then the address does not require onboarding. However, when onboarding multiple EVM addresses in a single transaction, contracts deployed to the bridge account cannot be accessed in the runtime since they are not available in the state space until after the transaction has completed.

Suggest A Solution

@lmcmz has mentioned that batch onboarding is a product requirement, so EVM address status will require some reworking. Unfortunately, the EVMAddress type cannot serve as an index to a mapping, at least not at the moment (though this may be possible by somehow ensuring the type is a HashableStruct). Instead, we could index on the serialized value of the EVM address and map to the associated Type. This would in essence be a reverse mapping of the FlowEVMBridgeConfig.typeToEVMAddress field.