Fix search

[A1Liu]

Bruh it's been utter garbo for so long it needs to NOT be garbo

just fix it with the not-garbo button bro it's so easy

The first implementation was done in StackOverflow-Style, where I just copied random shit from the postgres docs until it worked-ish. This time, I'm going to really actually read the docs before implementing it.

• Read the whole fucking thing this time please: https://www.postgresql.org/docs/current/textsearch-intro.html

Needs:

• Don't crash lol
• Faster speeds using generated columns and indices on those columns
• Weights on the data fields that makes the search return better results more often
• Partial word searches, or at least some kind of fuzziness
• Do some query profiling to get the latency lower; still slow in prod
• Do some more profiling; requests are still ~100ms

[A1Liu]

Going to close this, as Schedge v1 search in production right now times at ~150ms, so the current v2 time of ~75ms is OK enough to not block v2 beta release

The unfinished stuff from above is separated into another issue.