Ignore EVM errors when staging contracts

[joshuahannan]

Issue To Be Solved

When staging contract code that relies on the EVM contract, the staging reports errors about InternalEVM that should not be reported.

error: cannot find variable in this scope: `InternalEVM`
   --> 8c5303eaa26202d6.EVM:513:19
    |
513 |         let addr = InternalEVM.createCadenceOwnedAccount(uuid: acc.uuid)
    |                    ^^^^^^^^^^^ not found in this scope

error: cannot find variable in this scope: `InternalEVM`
   --> 8c5303eaa26202d6.EVM:524:15
    |
524 |         return InternalEVM.run(
    |                ^^^^^^^^^^^ not found in this scope

Suggest A Solution

Ignore the errors about the EVM contract.

Context

Some contracts that are trying to stage will show this error and it could mask other actual errors

[nvdtf]

Related onflow/cadence-tools#331
@jribbink I see the above is closed, is there further integration needed here?

[jribbink]

Related onflow/cadence-tools#331 @jribbink I see the above is closed, is there further integration needed here?

Yeah, this is a similar fix, fairly trivial effort. The LS & C1.0 update validator don't share the same codebase (there's some overlap, but was not really worth the effort to refactor given this tool is short-lived).

The caveat is that the fix for the LS exposes the InternalEVM contract to all locations. There's some added complexity to providing an alternate stdlib based on contract location.

A risk to making a similar fix here is that if someone erroneously uses the InternalEVM contract in their contract, the validator could give a false positive result (I don't know why they would do this/if this is an actual concern).

[jribbink]

Looked into it and I was able to do this using the evm.SetupEnvironment function, so the InternalEVM contract is only available to the EVM contract now and nowhere else.

#1697