feat!: add support for abi errors

[hal3e]

closes: #1648

Release notes

In this release, we:

• Added support for the new abi errors. See the RFC for more information.

Summary

• Updated fuel-abi-types to v0.12.0. This version supports the new error information.
• Refactored the sdk code to update the error description when a panic is encountered.
• Updated the forc commands in the CI to use --experimental error_type

For example, this sway code

struct B {
    id: u64,
    val: u64,
}

#[error_type]
enum MyError {
    #[error(m = "some error A")]
    A: (),
    #[error(m = "some complex error B")]
    B: B,
}

//-----> some contract or script code

panic MyError::B(B {
    id: 42,
    val: 36,
});

will produce this error message:

"panicked at: `contract_logs` - `src/main.sw:200:9` with message `some complex error B: B { id: 42, val: 36 }`"

Breaking Changes

• LogFormatter constructors renamed

  // old
  let fmt = LogFormatter::new::<MyLog>();
  
  // new
  // for ordinary logs
  let fmt = LogFormatter::new_log::<MyLog>();
  // for enums tagged with #[error_type]
  let fmt_err = LogFormatter::new_error::<MyError>();

• LogDecoder::new now needs the error-code map from the ABI

  // old
  let decoder = LogDecoder::new(formatters);
  
  // new
  use std::collections::HashMap;
  use fuels::core::codec::{ErrorDetails, LogDecoder};
  
  let formatters = /* HashMap<LogId, LogFormatter> */;
  let error_codes: HashMap<u64, ErrorDetails> = /* generated by Abigen or hand-built */;
  
  let decoder = LogDecoder::new(formatters, error_codes);

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)

[netrome]

Just some questions about the forc and sway patches that I'd like to get clarified before approving. Otherwise looks good to me.

[netrome]

Thanks for the clarification and update 🙏