Support named parameter type entry for sc build commands

[ixje]

Current behavior

Do after #623 is merged.

Currently the sc build_run and sc load_run commands require numeric entry of the contract parameter types defined in

neo-python/neo/SmartContract/ContractParameterType.py

Lines 29 to 39 in e378012

	Signature = 0x00
	Boolean = 0x01
	Integer = 0x02
	Hash160 = 0x03
	Hash256 = 0x04
	ByteArray = 0x05
	PublicKey = 0x06
	String = 0x07
	Array = 0x10
	InteropInterface = 0xf0
	Void = 0xff

Expected behavior

We can improve the user experience by allowing for named inputs, such that these numbers don't have to be remembered.

[LysanderGG]

I'd like to implement this.

I would suggest both complete names and some abbreviations, for instance "sig", "bool", "int", "str", "arr"

[ixje]

👌
ping @jseagrave21 to avoid double work; as you also indicated you might want to pick this up.

[jseagrave21]

@LysanderGG go for it! I started investigating yesterday but don't have anything written yet. cc @ixje

I would suggest both complete names and some abbreviations, for instance "sig", "bool", "int", "str", "arr"

I like that it would support both. The original issue was that we didn't want the user to have to remember anything proprietary.

My original thought was requiring a list entry (like params for RPC)
So, replace

070202

With

[string, integer, integer]

Also, I was toying with the idea of still supporting the original format. But that is definitely not a must imo.

[ixje]

I think it might be good to support the old format. There might be old tutorial out there that still use it, or people might prefer it (as it's less typing)