[VA-IIR 1041] WIP initial contact list loop setup

[john-rodriguez-adhocteam]

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

• This form will not be released to production yet (see the companion content-build PR below).
• Work for the VA-IIR team, which is creating a new review information form for the Welcome VA Setup process
• The ticket for the work is found here.
• We are setting up the initial contact info list loop so that we can make edits and changes requested by UX in subsequent tickets.
• The companion content-build PR to add this form to the registry.json—but not yet to prod—is found here.

Related issue(s)

• Ticket

Testing done

• Standard tests required by the generator are included.

What areas of the site does it impact?

• This is a new form app that does not affect other apps.

Acceptance criteria

• Match the initial configuration of the contact info list loop form

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

[nicksayre]

LGTM!

To run the site, first start the mock api:

yarn mock-api --responses src/applications/personalization/dashboard/mocks/server.js

Then in another console, build and run:

yarn build:webpack:local --env api="http://localhost:3000"
WEB_PORT=3001 node src/platform/testing/e2e/test-server.js --buildtype=localhost

Then visit: http://localhost:3001/my-va/welcome-va-setup/review-information/contact-information