feat(forge): cheatcode eip712

[0xrusowsky]

Adds a new cheatcode to safely generate hashes following the EIP-712 spec.

implementation details

ref #4818

due to the lack of polymorphism, it is not possible for the cheatcode to accept a struct. Because of that, users must provide a string.

this impl allows users to either pass:

1. the type name, which will we will attempt to retrieve from the bindings generated by forge bind-json
2. the full string representation of the type definition. In this case, we leverage alloy's eip712 support to generate the canonical representation of the type even if users pass malformed types (unsorted or with extra whitespaces).

example usage

string constant CANONICAL = "Transaction(Person from,Person to,Asset tx)Asset(address token,uint256 amount)Person(address wallet,string name)";

contract Eip712Test is DSTest {
    Vm constant vm = Vm(HEVM_ADDRESS);

    function testEip712HashType() public {
        bytes32 canonicalHash = keccak256(bytes(CANONICAL));

        // Can figure out the canonical type from a messy string representation of the type,
        // with an invalid order and extra whitespaces
        bytes32 fromTypeDef = vm.eip712HashType(
            "Person(address wallet, string name) Asset(address token, uint256 amount) Transaction(Person from, Person to, Asset tx)"
        );
        assertEq(fromTypeDef, canonicalHash);

        // Can figure out the canonical type from the previously generated bindings with `forge bind-json`
        bytes32 fromTypeName = vm.eip712HashType("Transaction");
        assertEq(fromTypeName, canonicalHash);
    }
}

[grandizzy]

Please run cargo cheats twice to fix failing tests

[grandizzy]

looks good, left couple of comments / nits!
So if I get this right the DX would be:

• generate bindings with forge bind-json (by default goes to utils/JsonBindings.sol but could be configurable to different pathToJsonBindings path)
• use vm.eip712HashType(typeDefinition) or vm.eip712HashType(pathToJsonBindings, typeDefinition) to generate EIP-712 representation

[grandizzy]

looks good, only some nits from my side before sending.

others, pls chime in re how the EIP-712 cheatcodes are designed to work and if you see any issue #10570 (review)
CC @klkvr

[grandizzy]

lgtm!

[0xrusowsky]

lgtm!

cool, let's wait for others to review and i'll merge it with the main feature branch.
Dani had to patch solar, so we won't be able to merge with master until there is a new release.

[grandizzy]

sorry, just realized params should be calldata and not memory