Enable "Auto-Cleanup" of Resolver Record fields

[lightwalker-eth]

Background Info

• This issue will likely require some special planning before we implement it. Suggestion is that we first use this issue to collect ideas about "Auto-Cleanup" of Resolver Record fields and then make a planning doc before implementation begins.
• https://docs.ens.domains/ensip/18
• https://docs.ens.domains/ensip/12
• https://docs.ens.domains/ensip/9#address-encoding
• https://docs.ens.domains/ensip/7
• https://docs.ens.domains/ensip/5

Goals

• ENSNode clients should be able to (optionally?) request that all resolver records returned will be both:
  • validated (ex: if a value is supposed to be a URL, it's a valid URL)
  • normalized (ex: if a value is supposed to be for a Twitter profile, we normalize all the ways a Twitter profile record might be formatted. Sometimes it might have a only a Twitter username (no '@' prefix), other times with the '@' prefix. Other times it might be a full URL to a Twitter profile on twitter.com, other times a full URL using a x.com URL, etc.. We should provide a mechanism for all of this to be completely predictable and normalized for our API clients so they don't need to worry about such complexities.

Examples

websiteUrl

The following screenshot is taken while reviewing PR 1024.

Related references

Please note: the references below should NOT be interpreted as being what we should do or how we should implement anything. Instead, they are just linked here to potentially serve as inspiration for how we might build our own implementation. Let's think for ourselves and decide for ourselves what is best.

• https://github.com/v3xlabs/ens-tools/tree/master/packages/format
• https://github.com/ensdomains/ens-app-v3/tree/5541991ed43fa7b39b483d8910e39b6528f19210/src/utils/records
• https://github.com/ensdomains/ens-app-v3/blob/5541991ed43fa7b39b483d8910e39b6528f19210/src/validators/validateAccount.ts#L2