Adds entry for supply reordering app under /my-health

[radavis]

Summary

• Adds entry for supply reordering app under the /my-health path

Related issue(s)

• Link to ticket created in va.gov-team repo
  Make application available in lower environments : Supply Reordering va.gov-team#97137

Testing done

• Verified that the local changes allow the react application to be served at /my-health/order-supplies

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?

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

[dcloud]

This looks good.

I don't recall if appName in the content-build registry or the one in the app manifest is used for the document title, but wanted to say something in case "Health Care Supply Reordering" isn't intended to be the user-facing title for the SPA. I could be wrong on multiple accounts.

[radavis]

@dcloud After looking through the following files, I believe the appName within the content-build registry determines the page title (unless overridden by the react app). Will have to investigate/experiment to know for sure.

• src/site/stages/build/plugins/create-react-pages.js
• src/site/includes/header.html
• src/site/includes/metatags.drupal.liquid

At the moment, I've set vagovprod: false so that we're only deploying to lower environments. Thanks for the info!

[nichia]

The entry looks good. I tried testing the new supply reordering app locally and looks like the appName in this content-build registry is used for the document title.