feat!: use total_gas and total_fee from tx status

[hal3e]

closes: #1394

Release notes

In this PR we expose the tx status from succeeded translations in our higher level APIs. The user can use the (if available) tx_status and tx_id from the following transaction APIs

• deployment
• transfers
• force transfers to contract
• withdrawals to base layer
• blob upload
• contract, script and predicate calls/simulations

Note that the TransactionCost's field gas_used was renamed to script_gas and a new field total_gas is added.

Summary

The GasValidation trait is removed. This trait was used to make sure that the script_gas_limit is set correctly. The script_gas_limit is either:

• 0 if there is no script code,
• set by the user,
• estimated by our builders
  so an additional check before sending the tx is redundant - By removing it we have one less dry run before sending the tx.

Breaking Changes

• Removed get_response_from method from CallHandlers
• CallResponse refactored and added tx_status: Success field
• Method get_response accepts TxStatus instead of Vec<Receipts>
• Method new is removed form CallResponse
• GasValidation trait is removed from transaction builders
• Accounts transfer method returns Result<TxResponse>
• Accounts force_transfer_to_contract method returns Result<TxResponse>
• Accounts withdraw_to_base_layer method returns Result<WithdrawToBaseResponse>
• Executable<Loader>'s upload_blob returns Result<Option<TxResponse>>
• Contract's deploy and deploy_if_not_exists return Result<DeployResponse> and Response<Option<DeployResponse>> respectively
  -TransactionCost's field gas_used renamed to script_gas

Checklist

• All changes are covered by tests (or not applicable)
• All changes are documented (or not applicable)
• I reviewed the entire PR myself (preferably, on GH UI)
• I described all Breaking Changes (or there's none)