[CDP] 94725 - Alert content updates

[Dr-Pongo]

Are you removing, renaming or moving a folder in this PR?

• No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)

⚠️ TeamSites ⚠️

Examples of a TeamSite: https://va.gov/health and https://benefits.va.gov/benefits/. This scenario is also referred to as the "injected" header and footer. You can reach out in the #sitewide-public-websites Slack channel for questions.

Did you change site-wide styles, platform utilities or other infrastructure?

• No

Summary

Updating alerts to match new content which includes more clear language on who to contact at VA.

Related issue(s)

• Link to ticket created in va.gov-team repo
  Alert Update for when the DMC endpoint times out va.gov-team#94725

Testing done

WIP

• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected
• Describe the tests completed and the results
• _Exclusively stating 'Specs and automated tests passing' is NOT acceptable as appropriate testing
• Optionally, provide a link to your test plan and test execution records

Screenshots

Overview Page

Overview page at `manage-va-debt/summary`

	Before	After
Both endpoints fail
Debts fail
Copays fail

Debt summary page

Overview page at `manage-va-debt/summary/debt-balances`

	Before	After
Both endpoints fail
Debts fail, copays available
Debts fail, no copays
Other VA section - Copay error

Copay summary page

Overview page at `manage-va-debt/summary/copay-balances`

	Before	After
Both endpoints fail
Copays fail, debts available
Copays fail, no debts
Other VA section - debt error

What areas of the site does it impact?

CDP Alert messages only
(Describe what parts of the site are impacted if code touched other areas)

Acceptance criteria

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

[OptionSelect]

LGTM! 🚀

[mgleo]

Looks good to me!