feat: vm.JumpTable override

[ARR4N]

Why this should be merged

Allows for creation of unexported vm.operations and their injection into vm.JumpTables through a registered hook.

First step to full support of #22.

How this works

Introduces vm.Hooks that can be registered via vm.RegisterHooks(). These are far simpler than params hooks as they don't need payloads. The vm.Hooks.OverrideJumpTable() hook is used in both NewEVMInterpreter() and LookupInstructionSet() to modify their respective JumpTables after creation. This couldn't be defined on params.RulesHooks due to a circular dependency.

The vm.OperationBuilder factory is also introduced to allow creation of the otherwise unexported operation type. I chose this pattern over a function because it makes arguments clearer at the usage site. To provide access to internal identifiers, the custom OperationFunc is an extension of the regular executionFunc to also accept an OperationEnvironment (similar to a PrecompileEnvironment).

How this was tested

Integration tests that demonstrate (a) honouring of the params hook signal; and (b) proper execution of a newly created *operation.