ensnode-sdk: Optimize EnsNodeClient's `resolveRecords` return types

[Y3drk]

Goal

Optimize EnsNodeClient's resolveRecords method so that the values of the addresses record are typed as NormalizedAddress.

Optimization of other return fields would also be welcome (if possible).

Why

• Requested by @lightwalker-eth here
• Would enhance DX, as it would allow the removal of typecasting when using the method (ex. here or here)
  • Without the typecasting, our typecheck check throws the following errors (on the examples listed above)

[coderabbitai]

🔗 Related PRs

#1575 - fix: add correct ensv1 and ensv2 addresses to sepolia-v2 namespace [merged]
#1873 - tests: add tests to ensapi using ens-test-env [merged]
#1908 - Refactor/enssdk refactor continued [merged]
#1932 - fix: minor fixes from copilot after big pr [merged]
#1938 - Using NormalizedAddress in referral program logic [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!