This is no longer needed because we do it elsewhere in a common matter

With the talk of supporting more than one wasm execution environment, make the decision on allowable opcodes in a central location which enforces white/black listing for each opcode. The hope here is that in a single file it is possible to review all opcodes, their constraints, and if they are blacklisted, etc

eosiod will refuse to run if an opcode is not dispositioned by some manner. Disappointedly, I had to do some copy pasta on most of the whitelisted opcodes due to current design. However, due to all methods in eosio_constraints_visitor being marked override, there is not much chance of an error here so I'd like to roll with this still.

the removal of `init` from `setcode` moved compilation AND validation of wasm to the first action.  We should do validation during `setcode` but doing this properly requires additional work.  This is a temporary fix

Additionally, the injector code was failing when hit with hand crafted wasm that had no types/import section(s)

Adding a few more constraints on the WASM execution environment. Some of these we’re well aware of but others are new constraints to aid performance and scalability.

* Limit initial linear memory size to 16 pages (1MB) maximum
* Limit linear memory initializers to the first page (first 64KB)
* Limit number of table elements to 1024
* Limit mutable globals to a maximum of 1KB
* Limit load/store offsets to a maximum of 1MB (matching maximum runtime size)

We've made the decision that sbrk is the way contracts will grow memory. So, remove access to WASM's standardized memory opcodes. As it stood, these subverted our expected memory management.