Tx error handling

[koxu1996]

We have handling for tx failures, after tx is broadcasted with sync mode:

gevulot-rs/src/base_client.rs

Lines 332 to 339 in ad1190d

	log::debug!("broadcast_tx response: {:#?}", resp);
	let tx_response = resp.tx_response.ok_or("Tx response not found")?;
	if tx_response.code != 0 {
	return Err(Error::Unknown(format!(
	"Transaction failed with code: {} ({})",
	tx_response.code, tx_response.raw_log
	)));
	}

Sync mode means that basic checks are done (structure, signatures, fees), and tx is added to the mempool. However, execution still can fail later.

Currently we fetch the tx response and blindly start parsing its message - even if tx code is non-zero - which results in Error: Unknown("no response message").

---

This PR improves handling with a dedicated Tx error: hash, code and log included.

For example, instead of "no response message" (like in gevulotnetwork/gvltctl#44), now you will get:

Error: Tx("A3469D4B4A2D046B41752FA8DFA7FA2787881126E3CF1C10AFE6CB3351EACDA7", 11, "out of gas in location: IterNextFlat; gasWanted: 106014, gasUsed: 106022: out of gas")