Travel Pay/change root url

[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

If the folder you changed contains a manifest.json, search for its entryName in the content-build registry.json (the entryName there will match).

If an entry for this folder exists in content-build and you are:

1. Deleting a folder:
   N/A

2. Renaming or moving a folder: Update the entry in the registry.json, but do not merge it until your vets-website changes here are merged. The content-build PR must be merged immediately after your vets-website change is merged in to avoid CI errors with content-build (and Tugboat).

NOTE:

• While I am not "renaming" a folder, I am changing the manifest.json and rootUrl for our application, so I will have a content-build PR to merge as well.
• Link to content-build PR
  PR #2385

⚠️ 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)
  Changing the rootUrl for our application to allow for future features.

Old URL: my-health/travel-claim-status
New URL: my-health/travel-pay

Also adding a sub-route /claims to consolidate all travel claim related pages. The root path (/) will redirect (using React Router <Redirect> component) within the mounted Travel Pay app.

The application has not yet been publicly rolled out, so a server-side redirect is not necessary.

• (What is the solution, why is this the solution)
  The initial rootUrl for the application as a whole was travel-claim-status but new features currently in development are not related to claim status specifically, so we needed to update the base URL to reflect new capabilities.

• (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)
  department-of-veterans-affairs/va.gov-team#98336 (MHV team issue to update on their landing page)

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

N/A

What areas of the site does it impact?

(Describe what parts of the site are impacted if code touched other areas)
Travel Pay
MHV landing page (currently the only entry point to our application on staging)
Appointment app (currently behind a different feature flag)

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

[ryanshaw]

VAOS files look good

[kjduensing]

🐸

[dcloud]

The change to src/applications/mhv-landing-page/utilities/data/index.js looks good!