feat: club and event search

[michael-brennan2005]

Club and event search.

Considerations before approval

• How should error handling work with search? If upserting/deleting a club or event fails, should we rollback in the outer club/event transaction that it was called in? Obv answer is no, but we should return an error at least. Is it bad go practice to both return a value and an error? I think that would get gross very quickly but idk. Key thing is its ok if something is in the DB but not in search.
• Right now there's a lot of repetition in codebase, its very obvious that clubs and events should be behind some "SearchObject" interface or something. What's tricky is that the interfacing/abstraction isn't just methods but also types - each object has a results type (what is returned from search endpoint, right now they are same and this is probably just a Results sort of type), document type (what acc gets uploaded to opensearch index), and query type (what filters/queries we can search type with). Im very tired so this may just be something I need to think about.
• Security for opensearch is striaght up disabled, but this is something I was gonna work on w deployment so

[garrettladley]

some nits then LGTM
great work on this MB @michael-brennan2005 ⚽🐐

[garrettladley]

LGTM good stuff @michael-brennan2005