test: add import compliance tests

[JonathanOppenheimer]

Why this should be merged

This PR prevents files inside of the vms/evm directory from importing packages within the graft/ directory.

• This is important because with the removal of coreth, there is not longer a natural boundary between the uplifted and non-uplifted code. We need to enforce such a boundary.
• This boundary is important, especially as other people individuals start work on properly uplfiting code post monorepo. Reviewers and developers may not be familiar with why we want this distinction to exist and programmatically enforcing this boundary will prevent mistakes and leakage of legacy EVM code into AvalancheGo.
• See this issue for additional context Remove libevm import restriction test from graft/ post merge. #4541

Closes #4541, #4643

How this works

The boundaries are as follows:

• graft/coreth can be imported everywhere in AvalancheGo except vms/evm.
  • However, vms/evm/emulate is an exception to this rule
• graft/subnet-evm can not be imported anywhere in AvalancheGo
  • However, vms/evm/emulate is an exception to this rule

How this was tested

Existing CI.

Need to be documented in RELEASES.md?

No

[JonathanOppenheimer]

Feel free to open a PR to move pseudo into internal/libevm instead of checking here. If I remember I'll do it myself but it's low priority so I may not get around to it soon.

I've done so! That PR is available here: ava-labs/libevm#250

I've removed the pseudo check from this PR, and also remove the tests this replaces. This PR is relevant as Austin and I worked through the subnet-evm monorepo PRs, with some assumptions that this PR enforces.

[JonathanOppenheimer]

The above PR is now merged in. Thanks to @maru-ava for the suggestion.

[alarso16]

This is definitely worth some more thought about exactly what we want to enforce, and the boolean logic is overly complicated (and incorrect I think)

[maru-ava]

lgtm but I leave it to an evm team member to merge.