feat!: beta-5 support

[hal3e]

This PR adds sdk support for beta-5.

• TODO: update docs and describe breaking changes

BREAKING CHANGE:

• TxParameters are replaced with TxPolicies
• GasPrice and Maturity fields are optional
• TxPolicies introduced new fields:
  • WitnessLimit - allows the limitation of the maximum size of witnesses in bytes.
  • MaxFee - allows the upper bound for the maximum fee that users agree to pay for the transaction.
• The ScriptGasLimit only limits the script execution. Previously, the ScriptGasLimit also limited the predicate execution time, but it is not valid anymore. So, it is not possible to use the ScriptGasLimit for transaction cost limitations. A new MaxFee policy is a way to do that. The GasLimit field was removed from the Create transaction because it only relates to the script execution(which the Create transaction doesn't have).
• The new WhitnessLimit also impacts the max_gas and max_fee calculation along with the ScriptGasLimit(in the case of Create transaction only WitnessLimit affects the max_gas and max_fee).
• The minimal gas also charges the user for transaction ID calculation.
• Each transaction requires setting the GasPrice policy.
• Previously, GasLimit should be less than the MAX_GAS_PER_TX constant. After removing this field from the Create transaction, it is impossible to require it. Instead, it requires that max_gas <= MAX_GAS_PER_TX for any transaction. Consequently, any Script transaction that uses MAX_GAS_PER_TX as a GasLimit will always fail because of a new rule. Setting the estimated gas usage instead solves the problem.
• If the max_fee > policies.max_fee, then transaction will be rejected.
• If the witnessses_size > policies.witness_limit, then transaction will be rejected.
• get_message_proof not uses Nonce instead of the message_id
• predicates do not use ChainId for address calculation
• manual_blocks_enabled is replaced with debug in local chain config
• fee_checked_from_tx uses FeeParameters
• fuel_tx::ConsensusParameters were refactored - this also affects us
• when building a transaction_builder the BuildableTransacion trait needs to be in scope
• utxo_validation and manual_blocks are enabled by default for test providers
• node config does not have local_node anymore use default - let node_config = Config::default();

Thanks @MujkicA for updating the documentation.

Checklist

• I have linked to any relevant issues.
• I have updated the documentation.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary labels.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.

[digorithm]

Adding to @iqdecay's

• I'm not sure I understand the logic behind renaming everything. To me, we are exposing implementation details to the user. As a user, using TxPolicies instead of TxParameters feels unusual at best. Also I feel like our responsability as the SDK is to shield the user from all the little internal changes the fuel-core or fuel-vm repos go through. So I'm not sure why we are replicating all these breaking changes in our API

Think of "transaction policies" as the new domain language here. This is coming from upstream (fuel-core), meaning that if we somehow wrap it around our own `TxParameters" language, we will be causing a lot of confusion in the future when this abstraction inevitably leaks. Sticking with one language is best for communicating. A lot of users will be talking about the configurations for transaction policies. If the SDK forces it to be called transaction parameters, it'll just be confusing!

[digorithm]

Thanks @MujkicA for the doc updates.

Code comments are also much better now.

Just a few nits left.

[iqdecay]

looking good! Thanks for your answers, it's clearer to me now. Left one formatting nit.

[digorithm]

LFG! 🚀