Refactor the PeepholeOptimizer into arbitrary passes

[ike709]

Changed the peephole optimizer to support arbitrary passes over the bytecode with different optimizations instead of trying (and failing) to do everything in one go, as opts like PushNFloats would break the GetOpcodes() checks of other optimizations.

IPeepholeOptimization has been renamed to IOptimization. Individual optimizer passes are the inheritor interfaces of this parent interface.

Here are the passes in order:

1. IPeepholeOptimization - Runs pretty much everything not involving PushN opcodes
2. IBytecodeCompactor - Converts multiple Push opcodes to PushN opcodes
3. IListCompactor - Converts PushN... CreateList to CreateListN... opcodes

I ran my usual bytecode analysis scripts on TG and confirmed that we're now running const folding optimizations (in the first pass) 100% of the time. I also confirmed that second-pass and third-pass optimizations are also being applied.

I booted TG and confirmed it doesn't explode. I also ran the profiler and confirmed that the performance impact is negligible:

Closes #2059

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[wixoaGit]

Instead of having the different interfaces for each pass, could we instead have a property that describes which pass each optimization is applied on? You could have a static const or enum to keep the naming of each pass. Like:

public int OptPass => IOptimization.PassListCompaction;

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.