Support searching agents based on multiple parameters

MR: Pending

Description

The proposed UI (see design section) has a search bar functionality that we have decided not to implement as part of the first iteration, see thread: #536924 (comment 2478178472). We might need to improve the UX based on user feedback to provide search functionality in the future.

This would entail backend changes and frontend changes to support searches

Backend

The current Query and associated finder only filter on Availability (mapped/unmapped); we would need to provide input that allows filtering on the following as well(subject to change on more discussion/feedback):

1. Group.
2. Project.
3. Cluster agent status.
4. Cluster agent name.

Frontend

Changes here would center around adding the search bar and using the search autocomplete APIs to support valid parameters that the backend query can use.

group search API call (from monitoring browser traffic) :

http://gdk.test:3000/api/v4/groups.json?search=gitlab&per_page=20&order_by=similarity

Project search API call after group selection (from monitoring browser traffic) :

http://gdk.test:3000/api/v4/groups/33/projects.json?search=flig&per_page=20&order_by=similarity&with_shared=false&include_subgroups=true

Project search API call (from monitoring browser traffic) :

http://gdk.test:3000/api/v4/projects.json?search=flig&per_page=20&simple=true&membership=true&order_by=similarity

API endpoints doc: https://docs.gitlab.com/api/api_resources/

Acceptance criteria

• Users can search for organization cluster agent mappings with the filters passed as arguments

Implementation plan