Rename CREATE3/4, *CALL2 instructions

[pdobacz]

Reasons to rename:

• current names were temporary names which lasted a bit too long
• avoid the sequel-based naming in instruction's mnemonics, conflicting with the PUSH1, 2, 3... convention
• avoid conflict with previous meaning of CREATE3 used in some contexts

EOFCREATE creating from within an EOF container
TXCREATE creating from a transaction
EXT* is for consistency with legacy EXTCODEHASH and the like
Lastly, abbreviated versions were slightly preferred (i.e. no EXTDELEGATECALL)

[rakita]

TXCREATE and EOFCREATE are great names, liking them a lot!

EXT* prefix is slightly weird but are a lot better than CALL2.

For EXTSCALL, EXTDCALL only downside of shorted names is they are harder to read. EXTCALLS and EXTCALLDare maybe more readable and are aligned with CALLF, wdyt?

[pdobacz]

For EXTSCALL, EXTDCALL only downside of shorted names is they are harder to read. EXTCALLS and EXTCALLDare maybe more readable and are aligned with CALLF, wdyt?

Thanks! To me personally EXTCALLS is a tiny tiny bit unfortunate, because is looking like plural "calls". Also less aligned with legacy "style". I'm going to move forward with this as is, since no strong objections were raised and for the sake of avoiding discussing this too long.