Travel Pay/unskip cypress test

[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)
  While updating the travel pay rootUrl the related cypress tests were failing so they were skipped in the interim. Now that everything is deployed and up to date we need to turn them back on.

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

Related issue(s)

• Link to ticket created in va.gov-team repo
  department-of-veterans-affairs/va.gov-team#98178(Team GH Issue)

• Link to vets-website PR
  PR #33498

• Link to content-build PR
  PR #2385

• Link to vsp-platform-revproxy PR
  PR #780

Testing done

• Describe what the old behavior was prior to the change
  Cypress tests were skipped
• Describe the steps required to verify your changes are working as expected
  Cypress tests now run and all pass

Screenshots

N/A

What areas of the site does it impact?

Travel Pay app

(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?

[IGallupSoCo]

LGTM