feat: use foundry-cheatcodes implementations

[DaniPopes]

Motivation

Unblocks all other cheatcode PRs.

Follow-up to #5998, #6128.

This PR deprecates foundry-abi, which will require another follow up to remove completely since it's still used for some trace and log decoding.

Solution

Replace old Ethers cheatcodes with new Alloy cheatcodes.

Breaking changes

• parse* and env*:
  • bool values are now parsed as strictly true|false instead of [tT]rue|[fF]alse
  • bytes32 values are not padded anymore when encountering less than 32 hex bytes, e.g. 0x0102 won't be padded to 0x0102000000000000000000000000000000000000000000000000000000000000 and instead fail parsing with "invalid string length"
  • Signed integers (not unsigned) don't fail parsing on non-prefixed hex anymore, e.g. ffff parses when it should fail because of missing 0x prefix. This is tracked here: [Bug] Signed::from_str should have the same behavior as Uint alloy-rs/core#387
• Reverts are now always encoded using the custom error CheatcodeError(string), instead of either the default Solidity revert (Error(string)) or an arbitrary signature (CheatCodeError)
• Error message strings in general have been changed to be more consistent and less confusing. This breaks tests that check for exact matches on cheatcode error messages, which is not recommended anyway because they may change at any moment.

[mattsse]

lfg!!!

one suggestion, otherwise lgtm, pending tests

[Evalir]

This is so much better—I think once tests pass we're good to go!

[refcell]

🔥