Fix cross chain resolver compatibility with resolver interface and ENS UI

[Chomtana]

Problem

Current cross chain resolver doesn't implement standard public resolver interfaces (IAddrResolver, IAddressResolver, ITextResolver and IContentHashResolver). Causing ENS UI to not support the cross chain resolver and show a warning on updating the resolver.

Solution

• Implement function according to IAddrResolver, IAddressResolver, ITextResolver and IContentHashResolver interface
• Implement IERC165 supportsInterface
• Implement callback return type handler system based on function signature (If from ExtendedResolver resolve function, return ABI-encoded response, otherwise, return actual response)

Additional Improvements

• Upgrade version of packages to fix build errors
• Use workspace:* for evmgateway dependencies

Test

We have tested our L1Resolver contract on https://web.getlaika.app/ and confirmed that it's working correctly on Sepolia <-> OP Sepolia CCIP Read.

However, I can't test on https://app.ens.domains/ because https://ccip-v2.ens.xyz/ post request has frozen forever. So, resolver records aren't loaded.

Note: disputegame.eth name hash is 0x438bfe3fc990665148f8ac1638323ab84054a5c22a1ab61fe63cebc3040129cb

[makoto]

Hi.
Thank you for the PR but I don't think we should expose the low getter functions (eg: addr, text) mostly because they won't be able to handle wildcard resolve takes dns encoded name and recuresively look for matching target which you cannot do with node

[Chomtana]

It seems to be an error on the Cloudflare function that prevents it from being resolved. Wondering why the manual test passed well.

• URL: https://op-gateway-worker.optidomains.workers.dev/REDACTED/0xea9cd3bf000000000000000000000000f079f2a30f3c797f8e6920ad783b74846a9acbf4000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000002000001ff000000000000000000000000000000000000000000000000000000000102200304ff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000000000000000016000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000020438bfe3fc990665148f8ac1638323ab84054a5c22a1ab61fe63cebc3040129cb0000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000020438bfe3fc990665148f8ac1638323ab84054a5c22a1ab61fe63cebc3040129cb000000000000000000000000000000000000000000000000000000000000000b6465736372697074696f6e000000000000000000000000000000000000000000.json
• Response: Invalid request format

[Chomtana]

That's because of REDACTED part. Changing that to a random wallet works.

I think @chainlink/ccip-read-server doesn't support REDACTED

[Arachnid]

Thank you for the contribution! However, as @makoto points out, this will not work on wildcard names - these methods will only function if the target has been set for the exact name, which is not what we want.

A better solution would be to fix the UI so that it doesn't warn like this on resolvers that implement these interfaces via resolve.

[Chomtana]

It appear that if we don't implement these addr, text and contenthash interface, ENS UI won't resolve the CCIP at all

ensdomains/ens-app-v3#732