extract base autoComplete class functionality for catalog filters

[rshewitt]

User Story

In order to reduce code redundancy, datagov wants to extract a base class for auto complete filtering

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN we have 3 autocomplete classes for filtering
  WHEN refactoring happens
  THEN a base class is created and each relevant child inherits from it \

Background

[Any helpful contextual notes or links to artifacts/evidence, if needed]

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]

[rshewitt]

comparing against current catalog we could still bring in topics and topic categories (let GSA approved AI summarize datasets to enrich docs?) and distribution formats as filters which would benefit from this refactor.