[WIP] - Aedp/aw/275/contact info prefill updates

[adamwhitlock1]

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 ⚠️

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

• Standardizing the Personal Information / Veteran Information page to adhere to the Prefill Pattern that was developed by our team.

• The overall structure would allow a function to be called to have a 'fully functioning' page to display the users name, date of birth, and last four of social security

• Optional configuration can be passed to function to do a couple other things to accommodate different teams

  • a dataAdapter can be provided to define where the data resides that is shown on this page from within the form data object. An example might be that the ssn lives nested inside the form data at veteran.lastFourOfSSN, so the this adapter can be used to specify that path, so the ssn is accessed correctly for the page to display it. The default is the path ssn
  • a personalInfoConfig object can be specified whether or not certain fields should be shown on the personalInformation page, because that is something that is present on some applications.
  • a custom error message can be specified if needed so that teams can customize the error alert that is shown

Related issue(s)

• Link to ticket created in va.gov-team repo
  department-of-veterans-affairs/va.gov-team#0000
• Link to previous change of the code/bug (if applicable)
  department-of-veterans-affairs/vets-website#0000
• Link to epic if not included in ticket
  department-of-veterans-affairs/va.gov-team#0000

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

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?