[gnokey] vm/qeval inconvenient parsing and non-existent erroring

[leohhhn]

Description

When I want to do a gnokey query vm/qeval, I would expect to be able to write a command like this:

gnokey query vm/qeval -remote https://rpc.gno.land:443 -data "gno.land/r/demo/wugnot BalanceOf("g1jg8mtutu9khhfwc4nxmuhcpftf0pajdhfvsqf5")" 

However, the quotation marks need to be escaped (smaller issue), and the command needs to be formatted in a very weird way, with a newline in the middle, which is super inconvenient for CLI commands:

gnokey query vm/qeval -remote https://rpc.gno.land:443 -data "gno.land/r/demo/wugnot
BalanceOf(\"g1jg8mtutu9khhfwc4nxmuhcpftf0pajdhfvsqf5\")" 

Also, if you do not do this, you will just get a 500 error and the transaction will break with no good response on why it happened:

❯ gnokey query vm/qeval -remote https://rpc.gno.land:443 -data "gno.land/r/demo/wugnot BalanceOf("g1jg8mtutu9khhfwc4nxmuhcpftf0pajdhfvsqf5")" 
--= Error =--
Data: unable to call RPC method abci_query, invalid status code received, 500
Msg Traces:
    0  /Users/sasurai/Desktop/gno/gno/tm2/pkg/crypto/keys/client/query.go:111 - querying
--= /Error =--

[leohhhn]

Same goes for vm/qrender - the following simply does not work, giving a 500 err message:

gnokey query vm/qrender --data "gno.land/r/demo/boards" -remote https://rpc.gno.land:443

Not sure if this is an error.

[leohhhn]

On top of everything, I think we definitely need to add a list of possible query arguments to gnokey query, as the only way to know them currently is the code/docs.

[linhpn99]

Why do we return both the code and message in ResultABCIQuery in case of an error? This helps easily determine the internal state of the application and selectively filter information to be returned

[linhpn99]

We could set the HTTP status code to always be OK, and only use the code from ResultABCIQuery

[thehowl]

We could set the HTTP status code to always be OK

Lol, no

Reminds me of the one time I added a pls200=1 querystring parameter to my API because I was using C# and didn't understand how exceptions worked (around 10 years ago)

Anyway, this bug seems to be mostly fixed for the gnokey --data inconvenience; maybe though we should still make the error messages show more information if available (and I think it is.)

[grepsuzette]

We could set the HTTP status code to always be OK, and only use the code from ResultABCIQuery

Instead of always returning an OK status, we could have gnokey show the ResultABCIQuery data even upon 4xx and especially upon 5xx, as in #2422.

See PR #2501