feat: add suggestion to unsupported cheatcodes

[Wodann]

Currently, unsupported cheatcodes report that they are explicitly unsupported in EDR+Hardhat, compared to Foundry.

In addition to this, it would be useful to allow per-cheatcode suggestions when we explicitly provide an alternative.

E.g. for:

    #[cheatcode(group = Utilities, status = Unsupported)]
    function eip712HashType(string calldata bindingsPath, string calldata typeName) external pure returns (bytes32 typeHash);

we could suggest:

Providing a path to a bindings file is not supported. Please use the eip712HashType(string calldata typeNameOrDefinition) cheatcode instead.

and even provide a link to Hardhat documentation.

[popescuoctavian]

Redirecting to specific error mesages or documentation pages can be done through matching the cheatcode name/signature.

EDR structured errors contain the cheatcode function signature in CheatcodeErrorDetails.cheatcode:

hardhat/packages/hardhat/src/internal/builtin-plugins/network-manager/edr/stack-traces/stack-trace-solidity-errors.ts

Line 280 in 3da2255

message = `Cheatcode '${stackTraceEntry.details.cheatcode}' is not supported by Hardhat.`;

cc: @Wodann