RpcTransactionResponse missing variant

[hlgltvnnk]

Currently, the RpcTransactionResponse does not cover all the possible result variants - according to nearcore execution outcome is optional
Which means that we can get error retrieving results of transaction with the status TxExecutionStatus::None (this can be useful for a fire and forget strategy) or even TxExecutionStatus::Included

Error:
near_api::errors::ExecuteTransactionError - Transaction error: Critical(TransportError(Invalid Response Payload (b"{\"jsonrpc\":\"2.0\",\"result\":{\"final_execution_status\":\"INCLUDED\"},\"id\":\"0\"}"): data did not match any variant of untagged enum JsonRpcResponseForRpcTransactionResponseAndRpcTransactionError)

This means that current implementation is blocking users of near api to use other execution statuses than TxExecutionStatus::Final
This issue blocks this pr

[r-near]

Related: near/near-api-rs#117