feat: search rate my professor reviews by meaning

[jaspermayone]

Part of #453. Stacked on #641.

Search Rate My Professors reviews by meaning, so "lots of group projects"
finds the reviews that say so in other words.

curl "…/api/v1/catalog/reviews?q=lots+of+group+projects&semantic=true"
curl "…/api/v1/catalog/reviews?instructor=fac_kw7coe30&sentiment=negative"

{ reviews(q: "team assignments", semantic: true, first: 10) { nodes { comment instructor { name } } } }

The admin review list gets the same search, with a "By meaning" box, and now
shows the comment it searches.

What this publishes

Review text was already stored, and /api/faculty already returns it to
signed-in users. This puts it on the unauthenticated catalog API, so it is
worth a second look before merging:

• Only reviews that carry a comment are returned. Ratings with no words say
  nothing a reader could search.
• Every review, and the meta of every page, names ratemyprofessors.com as
  the source, so a client can credit it and link back.
• instructor, sentiment, q, and semantic are the filters. Pages are 25
  by default and 100 at most.

Also in here

Catalog::FilterError is now the shared parent of the query objects' filter
errors, so the new ReviewQuery returns a 400 through the same handler that
SectionQuery uses, on REST and on GraphQL.

Tests

bundle exec rspec is green locally (1583 examples), covering the query
object, the REST endpoint, the GraphQL connection, and the admin search.

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}