[LIBSEARCH-801] Implement "clear active filters" designs for advanced search (Part 4)

[erinesullivan]

Overview

This pull request focuses on making changes to the DateRangeInput component. Below are the noted changes:

• Separated DateRangeInput from AdvancedFilter for easier access and control.
• Updated DateRangeInput to use number input types instead of text.
• Added styles for input[type="number"].
• Updated Multiselect with simpler logic, and to set advanced filters on load based on the current filters set by the URL.
• Moved logic for grabbing current and advanced filters into FiltersContainer to resolve the Selector unknown... warning.

Testing

• Make sure the PR is consistent in these browsers:
  • Chrome
  • Firefox
  • Safari
  • Edge
• Run accessibility tests:
  • WAVE
  • ARC Toolkit
  • axe DevTools
• Check advanced search and compare it to the current site.
  • Does it look and feel the same?
  • If there are filters set, do they carry throughout the datastore?
  • If you are given a direct link with filters applied to the URL, do those filters become active on load?