Enable Managed ENS Hosting For ipfstemporal.eth

[bonedaddy]

End result:

• The ability for accounts in the paid or partner tier to acquire ENS names under ipfstemporal.eth that correspond to their username. Example mine would be bonedaddy.ipfstemporal.eth.
• Ability to update content hash the name points to

Implementation Steps:

• Modify database table to allow indicating if they have claimed their USERNAME.ipfstemporal.eth managed subdomain. Only users in the paid/partner tier can claim this.
• Add API call that lets used trigger registering their name
• Add API call that lets them update the ipfs content hash
• Modify the Pay backend to facilitate broadcasting the tx, and waiting for confirmation.

Work for the blockchain side of things is being tracked in this pr, work for the API side of thigns is being tracked in this pr

[bonedaddy]

ENS Deployment Addresses:

• https://docs.ens.domains/ens-deployments

Deploying on private network (aka, simulated backend for testing):

• https://docs.ens.domains/deploying-ens-on-a-private-chain