chore(fw): extra opcode metadata - block opcode usage based on fork

[spencer-tb]

For tests that are marked valid from a specific fork, i.e Frontier don't allow opcodes that are introduced after the fork.

Ideally we extend each opcode class to include a Fork field, such that they can be accessed using something like Op.GASPRICE.Fork.

We could also add futher meta information such as gas costs, something like Op.GASPRICE.Gas that can be used to easily calculate the total gas cost of chained opcodes, utilized for verification in tests. I.e asserting the gas cost is expected or adding it to an sstore.