Typeahead validation implementation

Issue Description

There are two typeahead fields in the Facility Locator search process

These fields need to adopt the typeahead validation design which is used in the 526ez form.

Loom video of 526ez form validation

https://www.loom.com/share/6ed0253878124531bef08f28b58623f9

[ ] Update field validation and error messages consistent with the design used in the 526ez form.

[ ] When the Veteran begins to enter a value in the field, deletes it, and then attempts to search, the error message Please enter a condition or select an option from the suggestions is displayed.
[ ] When the Veteran types in a value which does not match (whether or not it is valid or gibberish), the closest matching items are presented.
[ ] Error validation messages/stylings appear only after a user has interacted with a particular field.
[ ] Error messages appear between the label and the input.
[ ] Error messages use thick border and padding to visually indicate the error message
[ ] The field border turns red in the error state.
[ ] Screenreaders announce the presence of an error.
[ ] The form field receives an aria-describedby attribute that references the id of the error message.

[ ] Attached to a Milestone (when will this be completed?)
[ ] Attached to an Epic (what body of work is this a part of?)
[ ] Labeled with Team (product support, analytics-insights, operations, service-design, tools-be, tools-fe)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
[ ] Labeled with Type (bug, request, discovery, documentation, etc.)