Expand PUSHBYTES2-PUSHBYTES74 to have human readable names

[ixje]

Currently the OpCodes PUSHBYTES2 - PUSHBYTES74 are auto generated based on continuous numbering. Because of that they do not have human readable names (e.g. when converting to strings).

This results in:

• poorly readable test vectors, e.g:
  

  neo-vm/tests/neo-vm.Tests/Tests/OpCodes/Push/PUSHBYTES10.json

  Line 73 in 937c0ff

  "nextInstruction": "10"

• violation of the (draft) test vector specification ([draft] Test vector specification #94). Therefore adding unnecessary parsing logic for other languages that are also trying to adhere to these test vectors.

  The specification reads:

  nextInstruction

  A String describing the human readable name of the next opcode to be executed.

  This member is REQUIRED.

This PR addresses the issues by expanding the instructions.

[codecov-io]

Codecov Report

Merging #141 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #141   +/-   ##
=======================================
  Coverage   80.55%   80.55%           
=======================================
  Files          45       45           
  Lines        4587     4587           
=======================================
  Hits         3695     3695           
  Misses        892      892

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 937c0ff...a42aacd. Read the comment docs.

[shargon]

I like it

[igormcoelho]

Very good you took the time to do that. I guess this will help more people to easily follow the opcodes logic.