Apply further protocol acceleration to "identity" lookups

[lightwalker-eth]

Goals

1. Apply a key protocol acceleration opportunity.
2. Further demonstrate how ENSNode is the best solution for apps building on ENS.

Definitions / Background

1. Let's define an "Identity Resolution" as the following sequence of events:
   1. A "Reverse Resolution" to determine the primary name of an address. This operation requires:
      1. A "Forward Resolution" of the reverseName for the address.
      2. A "Forward Resolution" of the address for the reverseName
   2. A "Forward Resolution" of all the resolver records desired for the primary name. Ex: avatar, Twitter profile, etc..

Note how the above operation requires at least 3 network round trips for each of the 3 "Forward Resolution" operations.

Please also note how the chain of operations referenced above matches the implementation in popular libraries such as viem or wagmi.

Idea

1. If we add support for "Identity Resolution" to our APIs, where the resolver records desired from the primary name (if any) are included in the "Identity Resolution" query, then there's a key protocol acceleration opportunity.
2. Specifically: During the "Reverse Resolution" to determine the primary name of an address, when performing the substep for the "Forward Resolution" of the address for the reverseName, concurrently (and optimistically) lookup all the other resolver records desired for the "Identity Resolution" request.
   1. If the returned address doesn't match, then we ignore any of the other resolver records we fetched.
   2. If the returned address does match, we can return all the other resolver records we concurrently fetched without need for another round trip of resolver record lookup operations.