Cheatcodes as per new std-forge library

[msooseth]

Goal

The way forge-std is doing things has changed. It no longer sets a value in ds-test, but instead Revert-s with a specific message. So we have to match:

forge test --match-test "test_set_get()" -vvvv
[...]
  [31205] MateFailContractTest::test_set_get()
    ├─ [22216] MateFailContract::set_mate()
    │   └─ ← [Stop]
    ├─ [268] MateFailContract::get_mate() [staticcall]
    │   └─ ← [Return] 3
    ├─ [0] VM::assertEq(2, 3) [staticcall]
    │   └─ ← [Revert] assertion failed: 3 != 2
    └─ ← [Revert] assertion failed: 3 != 2

Instead of the current:

Traces:
  [42786] MateFailContractTest::test_set_get()
    ├─ [22216] MateFailContract::set_mate()
    │   └─ ← [Stop]
    ├─ [268] MateFailContract::get_mate() [staticcall]
    │   └─ ← [Return] 3
    ├─ emit log(val: "Error: a == b not satisfied [uint]")
    ├─ emit log_named_uint(key: "      Left", val: 3)
    ├─ emit log_named_uint(key: "     Right", val: 2)
    ├─ [0] VM::store(VM: [0x7109709ECfa91a80626fF3989D68f67F5b1DD12D], 0x6661696c65640000000000000000000000000000000000000000000000000000, 0x0000000000000000000000000000000000000000000000000000000000000001)
    │   └─ ← [Return]
    └─ ← [Stop]

The most prominent part of this change is the disappearance of line 202 from UnitTest.hs, where we'd check for failure bit being set in the cheat contract (i.e. 0x7109709EC...)

Implementation

• Emilio has changed things around already in EVM.hs to have a separate frame, which allows this to be coded in a relatively compact way. I have now added a number of required (but not all) cheatcodes.
• Moved all relevant test cases to std-forge/Test.hs and {Test} from ds-test/test.hs and {DSTest}
• Added most of the required assert... methods, though some are still missing. The ones still missing would require dynamic ABI handling, such as assertTrue(uint,string), where string is dynamic.
• Fixed the function signature generation for types such as tuples. Now prove_tuple_fail1(uint256[5] memory amounts) actually works
• Better debug output. Cleaner and more thorough. It should be a lot easier to debug things.

Future work

I haven't added:

• assertEq(T[], T[]) type asserts
• assertNotEq(T[], T[]) type asserts
• assertXXDecimal
• `assertApproxXX
• assertEqCall`

Mostly due to the above mentioned issue with dynamic ABI type issue.

TODO in a future PR

• Move cheatcodes into a new file
• Would be nice to accumulate errors when e.g. we have trouble with cheatcodes

Checklist

• tested locally
• added automated tests
• updated the docs
• updated the changelog

[msooseth]

This is not used anywhere, so I'm removing it

[msooseth]

This is now ready to re-review, @d-xo and maybe @blishko in case you want to have a go at it :)

[msooseth]

We don't store failures here any more in forge-std, so no need to check.

[d-xo]

we might wanna keep this around for a while as a compat mode? maybe with some cli flag --assertion-mode <ds-test|forge-std>?