MHV-61855 Added MHV API Gateway config settings

[mmoyer-va]

Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.

Summary

• Added configuration for MHV API Gateway migration
• Corresponding devops PR: https://github.com/department-of-veterans-affairs/devops/pull/15124

Related issue(s)

MHV-61855 - Implement/configure updated tokens in lower environment (endpoint changes)

• Configure this token in a lower environment, which will include adding a token as a secret in AWS.
• Document all the steps

Feature Flag Y/N ?

DataDog Analytics Y/N ?

Manual Testing Y/N ?

Automated Testing Y/N ?

Accessibility Testing Y/N ?

UCD Validation Y/N

Acceptance Criteria:

AC1 Configuration is complete

AC2 Steps are documented

Testing done

• This step is just adding configuration. The new endpoints have been tested, but pulling environment variables will have to be tested in a review instance or staging as we transition our endpoints to the new Gateway.

Screenshots

The AWS Params

What areas of the site does it impact?

• Just new config for now, but will eventually be used by all MHV on VA.gov applications

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature