85787 Update confirmation page - form 10-10d

[michaelclement]

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

• No, I'm not changing any folders (skip to Summary and delete the rest of this section)
• Yes, I'm removing, renaming or moving a folder

Summary

This PR updates the confirmation page copy of form 10-10d.

• Hides the "Get Help" footer only on the confirmation pages for CHAMPVA forms (information is not accurate for this subset of forms on the confirmation page, but is useful during normal form flow)
• Updated "what happens next" copy
• Updated mailing/faxing copy
• Team: IVC CHAMPVA
• Flipper: in use

Related issue(s)

• Update confirmation page copy for 10-10d va.gov-team#85787

Testing done

• Manual
• Verified unit tests run and pass

Screenshots

	Before	After
Desktop

What areas of the site does it impact?

IVC form 10-10d (Confirmation page, Get Help footer), IVC form 10-7959c (Get Help footer)

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

⚠️ Team Sites (only applies to modifications made to the VA.gov header) ⚠️

• The vets-website header does not contain any web-components
• I used the proxy-rewrite steps to test the injected header scenario
• I reached out in the #sitewide-public-websites Slack channel for questions

Requested Feedback

NA

[micahchiang]

Couple comments about web component usage, but not a requirement.

[micahchiang]

I think it's relatively common for phone numbers to be clickable. Should this be a va-telephone component?

[michaelclement]

Updated in this commit - thanks!

[micahchiang]

I know it isn't part of this PR, but you could make this a va-link-action component if you wanted to 😄

[michaelclement]

Updated in this commit - thanks!