rusk-wallet: Implement http contract query

[Daksh14]

Closes #3108

Deploy my_first_contract.wasm Copy the generated contract_id and then contract call increment function 4 times

> Contract call transaction hash: 128b39f5ef8da2e1ddaacccebab29b176d51181e369e29c50ba1bc694cc34752
> Http contract query: <empty>

Then call read_value

> Introduce string for function name to call: read_value
> Introduce hex bytes for arguments of calling function:
> Introduce the gas limit for this transaction: 2000000000
> Introduce the gas price for this transaction: 1 LUX
> Contract call transaction hash: c49d238afa74a563fe8f73167a94f42a5f8b1cea526e9e753f294c45cb1c1a1e
> Http contract query: 4

Only supports u32 return values

[herr-seppia]

Why do you request gas price for contract query?
Why there is a transaction has for those query?

[miloszm]

return value from http_contract_call should be Option<Vec<u8>> IMO

[herr-seppia]

Just to be clear

There is NO need to create a transaction to to query a contract, so I don't get which tx_hash this snippet refers to

                let http_call = wallet
                    .http_contract_call(contract_id, &fn_name, &fn_args)
                    .await?;

                Ok(RunResult::ContractCall(tx.hash(), http_call))

[Daksh14]

@herr-seppia The http contract call is done alongside already existing tx contract call so if you do contract call it will send both the transaction and the http request to return values

[herr-seppia]

What's the need for sending both?

[Daksh14]

@herr-seppia I combined them because if you wanna call increment you need to do tx contract call but if you wanna call read_value you need to do http contract call.

If you want I can separate them that might save gas fees but the user might be confused

[miloszm]

this will give really ugly output, use hex::encode(bytes)

[herr-seppia]

Don't mix the transactions and the queries pls

About "save fees", there is no fee to save, since the query is free

[Daksh14]

@herr-seppia Just so you know I'm aware the query is just an http request it not a transaction and there's no fees involved, I said fees because we might wanna do http call and not transaction contract call so that might save fees but I'll seperate both of them now I thought it made senese to do both of them together