Added custom domain functions to admin panel

[kurtisassad]

Link to Issue

Closes: #8226
Closes: #7683

Description of Changes

• Adds ability to add and update new custom domains on admin panel

Test Plan

• Add HEROKU_APP_NAME, HEROKU_API_TOKEN, MAGIC_API_KEY, and MAGIC_CLIENT_ID to .env
• Go to http://localhost:8080/admin panel and make sure you are logged in as a super admin.
• Refresh existing custom domain and ensure it returns data
• Try refreshing a non-existing custom domain and ensure it returns error
• Try adding a new custom domain to a community. Then try refreshing it to ensure it returns data.
• Try adding the same custom domain twice, make sure it throws an error

Deployment plan

• We need to add MAGIC_CLIENT_ID to the environment variables as it is not there currently

[timolegros]

@kurtisassad as part of this PR can we add a Knowledgebase entry that lists all the places where we need to whitelist custom domains (e.g. Alchemy, Magic, etc)?

Never mind it seems to be there already. That said, we need to somehow keep track of when growth is linking a new custom domain because Alchemy and Magic (not sure about Magic) don't have APIs to update their whitelists programmatically.

[timolegros]

Per my previous comment, how do we deal with Alchemy whitelisting? Since they don't have an API to update the whitelist we need to manually add domains to the whitelist. Most chain interactions from a custom domain for an EVM community will fail unless we add that community to the whitelist. This should be very clearly outlined to Growth and it does mean that Growth still needs to create a ticket when adding a Custom domain for EVM communities.

[kurtisassad]

Discussed with Tim, we will get this in first and then figure out the alchemy whitelist flow, there seems to be some docs on generating a JWT, so we can go with that approach when he comes back from vacation

[jnaviask]

@timolegros my question is what direct onchain requests do we actually make on custom domains / how large is the breakage surface area in practice?

[timolegros]

@timolegros my question is what direct onchain requests do we actually make on custom domains / how large is the breakage surface area in practice?

1. Cannot load the community if it has stake or contests enabled
   
2. Cannot create stake/contests

[jnaviask]

@timolegros @kurtisassad IMO it is acceptable to get custom domain automation out where growth needs to make an eng request if stake/contest support is needed. Better than the current flow.

[timolegros]

LGTM just 2 quick suggestions.

[masvelio]

small comments but looks good to me in general, didn't test it manually though