Create ENS resolver in a public endpoint. Connect resolveName to this with a fetch

TLDR: Just do a fetch to this for now https://api.ensideas.com/ens/resolve/daws.eth

---

Because resolving ENS names requires heavy packages for unicode normalization, we should first enable ENS resolution in this package by connecting to a resolver endpoint via fetch.

This comes with many trade-offs, so consider this a temporary solution.

The primary trade-off is that using ENS resolution in this package would require a constant public internet connection. Previously a user of this package could be referencing their own eth node offline with no issues.

This is a temporary solution until normalization packages can be reduced in-size upstream via #144

Start at the resolveName entry point and inspect how name resolution currently uses the user's Ethereum node. Run the existing test suite before connecting it to https://api.ensideas.com/ens/resolve/daws.eth via fetch. Done means resolveName can use the endpoint while preserving the package's existing behavior and documenting the public-internet trade-off.

Written by the indexing model from the issue text.