Change search pattern across the application

Proposal

We should switch to a more traditional search pattern, where a user fills in a search form, the application queries the database, and returns a small set of results for the user to then take action against. For example, when directly adding people to a workshop, the admin would type a name into a search bar. They click 'search' and receive a list (or possibly just one) result. They click on the result and then take action.

Why this?

The application was originally built without realising how massive our chapters would get. As a result, we load hundreds of Member records into the frontend, and then filter them using javascript. This slows the application down and makes it really difficult to use for admins.

Why now?

We've got a small team set up around maintenance, and this would be a significant quality of life improvement.

Start by tracing the admin flow for directly adding people to a workshop, including the current JavaScript filtering of loaded Member records and the database query path. Define the search form and result-selection behavior before choosing an implementation. Done means admins can search for a small result set and act on a selected person without loading hundreds of records into the frontend.