fix: point Sepolia ensPublicResolver at the V1 resolver

`ensPublicResolver` is a V1 contract key: it sits in the v1 group of
`supportedL1Contracts`, mainnet holds the V1 address, and every reader is
a V1 action — `dns/importDnsName` and
`wallet/v1/{setPrimaryName,createSubname,wrapName}`. Each passes it as the
resolver for a V1 registry write, so it must implement the legacy `addr`
interface.

3799148 repointed the Sepolia entry at the V2 public resolver, which does
not implement it (`supportsInterface(0x3b3b57de)` returns false).
`DNSRegistrar.proveAndClaimWithResolver` consequently reverts inside
`setAddr`, making onchain DNS import impossible on Sepolia; the other
three actions are broken the same way for anyone calling them.

Verified against a Sepolia fork: with 0x8FADE66B… the import lands and the
V2 UniversalResolver reads the name back through ENSV1Resolver. That
address is also what live Sepolia names (ens.eth, nick.eth, test.eth)
resolve through today.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: v1rtl

packages/ensjs/src/clients/l1.ts

@@ -156,8 +156,12 @@ export const ensL1Contracts = {
     ensNameWrapper: {
       address: '0x0635513f179D50A207757E05759CbD106d7dFcE8',
     },
+    // The V1 PublicResolver. Only V1 actions read this key (dns/importDnsName,
+    // wallet/v1/{setPrimaryName,createSubname,wrapName}), and they pass it as a
+    // resolver for the V1 registry — so it must implement the legacy `addr`
+    // interface. The V2 public resolver does not, and belongs under its own key.
     ensPublicResolver: {
-      address: '0x5239A812ec9A62F46dbb5de8f346C8eFe7553A9f',
+      address: '0x8FADE66B79cC9f707aB26799354482EB93a5B7dD',
     },
     ensLegacyRegistry: {
       address: '0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e',