58745 VAMC updates

[christinec-fftc]

Summary

-Remove text and update text on the va-medical-records page
-Make the Name of VA medical facility input field free form instead of autosuggest from pre-defined list
-Cleanup unused code

Related issue(s)

department-of-veterans-affairs/va.gov-team#58745

Testing done

• Describe what the old behavior was prior to the change
  Prior to this change the facility name was using auto suggest, but users would get stuck here since the api is not working

• Describe the steps required to verify your changes are working as expected

1. Start fllling out an original claim
2. When you get to the supporting-evidence/evidence-types page, select 'VA medical records' for evidence types. Continue to the next page
3. Verify you can type in a facility name, other required fields and then save or continue
   Note : the behavior of the array list component is to do a scroll up when clicking the save button (it will not collapse until you click 'Add another facility' button)
4. Complete the rest of the 526 form and verify you can submit successfully

• Describe the tests completed and the results
  Manual: created and submitted (original) claims with both new and rated conditions
  Unit: minor updates for unit tests
  e2e tests: verified all tests still working

Screenshots

What areas of the site does it impact?

526EZ form on the va-medical-records page

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

[mchae-nava]

LGTM!

[mchae-nava]

Appreciate the clarifying comment. This is pretty neat, and I'm curious how this check works. Definitely makes things so much more convenient for veterans