refactor: uplift combined warp package from evm repositories

[JonathanOppenheimer]

Why this should be merged

There are packages in subnet-evm and coreth that share a lot of functionality / are mirrored. These packages should be uplifted to AvalancheGo to prevent the duplicative maintenance of two sets of the same code. This is part of that effort. This would close #4129 .

How this works

This code represents the 'merged' difference of coreth/warp and subnet-evm/warp. The two packages diverged significantly, and deference was given to additions.

Key merges:

• Used snowtest.Context() when snowctx is needed (defer to coreth)
• When the ValidatorReader is needed, imported it from warptest
• Deferred to verifier_stats.go from subnet-evm
• Deferred to verifier_backend.go from subnet-evm
• Deferred to backend_test.go from subnet-evm
• Used libevm RPC

Note:

• There are now 5 different Validator types, of varying similarity declared across AvalancheGo, from Stephen 5 years to Draco 3 months ago. This doesn’t seem clean to me.

Linting changes can be viewed standalone in 017a635

How this was tested

This is currently 'dead' code; after a new AvalancheGo release is dropped, we can use the code in the evm repositories.

Need to be documented in RELEASES.md?

No

[github-actions]

This PR has become stale because it has been open for 30 days with no activity. Adding the lifecycle/frozen label will cause this PR to ignore lifecycle events.

[JonathanOppenheimer]

FYI: I plan to review this PR thoroughly myself first, i.e. leave comments etc. and clean it up before seeking external review. This PR is finally passing CI now though!

[JonathanOppenheimer]

what happens if we put the message in the database but for whatever reason fail to sign the message and put it in the cache (I actually do not know)

[JonathanOppenheimer]

Blocked by #4767

This is no longer blocked and ready for review.

[joshua-kim]

When naming, a general guideline is to avoid having multiple names for the same logical concept unless we need to disambiguate - since this is a warp.DB we should call this warpDB rather than a warpMsgDB because there aren't other warp.DB's in this context.

If we find that consumers are frequently referring to a type in a common way it might suggest that the type needs renaming.

[JonathanOppenheimer]

There is already a variable called warpDB declared in the VM struct:

avalanchego/graft/coreth/plugin/evm/vm.go

Lines 218 to 220 in 5213f1c

	// [warpDB] is used to store warp message signatures
	// set to a prefixDB with the prefix [warpPrefix]
	warpDB database.Database

I assume Msg was added to differentiate these two databases.

[joshua-kim]

Marking as frozen -- this is no longer a current priority.

[JonathanOppenheimer]

Marking as frozen -- this is no longer a current priority.

Putting this in the backlog until we revisit it.