100025 Travel Pay, SMOC submission confirmation content

[seesleestak]

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.

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)
• Yes, I'm removing, renaming or moving a folder

⚠️ 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
• Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

• (Summarize the changes that have been made to the platform)

  Add content for SMOC submission confirmation page

• (Which team do you work for, does your team own the maintenance of this component?)

  Travel Pay

• (If using a flipper, what is the end date of the flipper being required/success criteria being targeted)

  Phased rollout beginning Feb 2025

Related issue(s)

• Link to ticket created in va.gov-team repo
  Add content to Confirmation Page [SMOC flow FE] va.gov-team#100025
• Link to epic if not included in ticket
  INITIATIVE: Simple Mileage-Only Claims va.gov-team#83829

Testing done

• Describe what the old behavior was prior to the change
  Before the changes the page was only a stub with a title
• Describe the steps required to verify your changes are working as expected
  I added a short circuit in the SubmitFlowWrapper to get the confirmation page showing without necessary logic

  useEffect(() => {
    setPageIndex(5);
  }, []);

• 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

Note: This field is mandatory for UI changes (non-component work should NOT have screenshots).

	Before	After
Mobile
Desktop

What areas of the site does it impact?

Travel Pay only

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

[seesleestak]

Like #34032, these are changes applied from #33664 in order to break it down into smaller chunks.

[liztownd]

Left a couple small comments, but overall LGTM. 🎉

[kjduensing]

Looks good! 🚂

[rmessina1010]

LGTM