Flatten type hierarchy removing single-implementation types

[codefromthecrypt]

#79 removed the naivevm interpreter implementation leaving what we called wazeroir. We had to name the other implementation because there were multiple possibilities. In reality the maintenance of multiple stores implies another will never live. Let's try to reduce the amount of types and packages knowing there is only wazeroir. Part of this could be "denaming" wazeroir as it becomes the default and only impl. Any other opportunities to flatten package and type hierarchies, and generally concepts or terms should be taken as well!

[codefromthecrypt]

one thing I noticed starting this is that compiler/operations.go has a lot of conceptual overlap with instructions.go most of the symbols have an exact or near match with opcodes, for example. This is probably an area we can be more direct.

[codefromthecrypt]

everything is internal now so we can do any of this without impact. in fact, we've already done a lot of this