feat: stateful precompiles + allowlist hooks

[ARR4N]

Why this should be merged

Introduces:

1. Stateful precompiles
2. CanExecuteTransaction and CanCreateContract hooks (equivalent to subnet-evm allowlists).
   a. Although this makes for a larger PR than I'd have liked, I thought it was important to demonstrate how the equivalent ava-labs/subnet-evm functionality can be achieved.

How this works

Hooks

CanExecuteTransaction() is called from core.StateTransition.TransitionDb() and CanCreateContract() is called from vm.EVM.create() (the common path for EVM.Create() and EVM.Create2()). If they return nil then functionality continues as normal, otherwise their errors are propagated.

Stateful precompiles

The PR introduces into core/vm:

type vm.StatefulPrecompileRun func(...) ...
// and
func NewStatefulPrecompile(StatefulPrecompileRun, ...) PrecompiledContract

Note that the constructor returns the same interface as ordinary precompiles, allowing the returned value to use regular geth plumbing (including the existing PrecompileOverride hook). However, the concrete type that it returns has special-case handling when running precompiles.

How this was tested

Both hooks result in unhappy paths when working correctly so their integration tests assert the equality of returned errors, which carry all externally injected arguments to demonstrate correct plumbing. CanExecuteTransaction is tested via core.ApplyMessage() while CanCreateContract is tested via EVM.Create() and EVM.Create2().

Stateful precompiles have integration tests exercised via the PrecompileOverride hook and vm.EVM.Call(), also demonstrating full plumbing of arguments.

The hookstest package is introduced to simplify registration of hooks for testing.