Parse revert error codes to determine more specific reasons for revert

[camsjams]

Motivation

Every Revert has a specific code that enables it to treat the log in different ways
https://github.com/FuelLabs/fuel-abi-types/blob/a340a110ded4268ca834269cb5916b9ac9b90943/src/error_codes.rs#L3-L16

In the case of a revert of a type required "0xffff_ffff_ffff_0000", we can safely get the previous log data from the log stack.

Usage example

No response

Possible implementations

1. improve our parsing of the revert to better utilize the different types of revert codes
2. This would allow us to have five types of revert cases now to better help DX, they'd have a better understanding of why something failed:

FAILED_REQUIRE_SIGNAL
FAILED_ASSERT_EQ_SIGNAL
FAILED_ASSERT_SIGNAL
FAILED_SEND_MESSAGE_SIGNAL
FAILED_TRANSFER_TO_ADDRESS_SIGNAL

Three part update to improve DX for #634:

1. This one
2. Update enum support
3. Use better enums in errors