Travel Pay / flesh out SMOC introduction page

[liztownd]

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 to Introduction page; refactor Help Text and update where it was used; add mock data for user + appointment

• (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
  #92353
  #10016
  #10015

• Link to epic if not included in ticket
  #83829

Testing done

• Describe what the old behavior was prior to the change
  The Introduction page for our submit mileage claim form flow was a shell, now it has data (hardcoded) and content.
• Describe the steps required to verify your changes are working as expected
  Locally: Start the mock api with yarn mock-api --responses src/applications/travel-pay/services/mocks/index.js; Build locally with yarn build:webpack:local --env api="http://localhost:3000" then serve the build with WEB_PORT=3001 node src/platform/testing/e2e/test-server.js --buildtype=localhost (instructions in README).
• Describe the tests completed and the results
  New Cypress test to test the flow through the form; New unit tests to verify each component including the new Introduction Page component.

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 directory 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

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

[seesleestak]

Working well for me 👍