Feature/update special filter UI and create any/none/fuzzy query params

[aswallace]

Description

A Big Ticket! This PR includes:

• ~UX updates to the special filter types (date, numerical range, search box with fuzzy search)~
• Logic for fuzzy searching (transferred over from #154 )
• Logic for any/none filters (include/exclude query params)
  • Corresponding UI for this in annotation filter form

closes #53 , closes #74

~TODO: fix font (#235 )~

Testing

• New & updated unit tests
• Tested manually with an EC2 instance of FES (the local version has the fuzzy search changes, but hasn't been deployed) and staging version of Mongo.

Screenshots

EDIT: Updated screenshots 9/30/2024

Any/none option

~The radio buttons are a little off center with Helvetica, but I think it will be fixed when we're using the correct Open Sans link~

Search box with new fuzzy search toggle (exact/non-fuzzy by default)

Date range with filter type choice group

Numerical range with filter type choice group

[aswallace]

CHANGES FROM PREVIOUS VERSION

Added a new optional type arg to filters in 181067e, so now filters can be exclude (null), any value, fuzzy, or default (regular filter) (open to changing the names of these). This allows us to get rid of a lot of the duplicate logic I had before, especially for redux and the AnnotationFilterForm component.

This means the FileExplorerUrl (our local BFF url parsing class) will NOT have the fuzzy/include/exclude params that I'd added in before, since now all filters are part of the filter param but with an extra type arg. However, the queries we send to FES do still need the new query params.

• Because of this, I kept (but simplified) the FuzzyFilter, ExcludeFilter, and IncludeFilter subtypes, bc even though they don't add new logic, they're a helpful shorthand for creating those filters. Could be convinced that they are unnecessary

Also no longer includes the unrelated UX changes to the modals since was merged in #250