Make a working prototype to set a single DNS record on a program domain

[h-m-f-t]

Issue description

To concretize what we're learned to date, we should make a working prototype that allows a team member to do what the title says.

This is just an exercise to make sure we have something quickly that is using the api, and is NOT meant to be reusable or good code, nor do we need to follow the usual best practices with fields (such as checking accessibility, performing form validation, showing errors etc ). In fact, we don't want this to be about about creating models and laying down architecture at all, so do not use models or store record info. Instead we can check if the record setting worked through other means.

Acceptance criteria

• [After a feature flag is enabled] allow any domain manager for igorville.gov to set a single DNS resource record (A or TXT on the /domain/#/dns page, or a subpage
• the feature flag is added and a new credential is now being used for the tenant key (update documentation accordingly)
• The record set above is visible to the internet (ie, dig a a.igorville.gov returns the record that was added)

Out of scope

• creating models
• showing which fields are required
• conditionally showing/hiding fields
• error handling for user input
• using the "settings" field on the DNS record(this has a LOT of fields and will be easier when using models)

Additional context

• This can be hideous and not well designed, but it should work and anyone on the internet should be able to see that the record exists.
• It would be nice to allow a user to supply the record's hostname (e.g., A record is at a.igorville.gov), as well as the value for the record.
• Can limit the types of records (such as A and TXT)

Note: You can hard code this for igorville , but do not make any commit containing with igorville's account id or the tenant id token. Use getgov-credentials and your local .env file instead.

Links to other issues

No response

[h-m-f-t]

We discussed this in planning today and agreed to revisit this next sprint planning. We'll see then if we're on track to deliver in 60 or if this needs more decomposition. Refinement tag added to make sure we look again.

[abroddrick]

We say a "single dns record" but then also mention limiting it to "A" and "txt" records, is that "and" a typo? Or do we want the AC to be able to set either. (Either is doable, you will just have one field that exists on txt and not an A). CC: @katypies and @h-m-f-t