feature: query filter support for common SQL keywords

[michael-genson]

What type of PR is this?

(REQUIRED)

• feature

What this PR does / why we need it:

(REQUIRED)

This extends our pagination query filter parsing to include various common SQL keywords:

• IS (only in conjunction with NULL)
• IS NOT (only in conjunction with NULL)
• IN
• NOT IN
• LIKE
• NOT LIKE

And an additional "fake" keyword:

• CONTAINS ALL

To accomplish this, two major changes were made:

1. The filter string parser needed additions to correctly understand lists (i.e. values between brackets)
2. The query builder was completely redone to leverage SQL Alchemy's ORM. Previously it constructed the raw (parametrized) SQL text

---

With these changes, you can make some powerful queries. Here are a few example Recipe queries:

• recipeCategory.name IN ["American", "German"]
• tags.name CONTAINS ALL ["soup", "chicken", "easy"]
• tags.name NOT IN ["small", "medium"]

You can also completely replace the custom filters we made for frontend filtering (more on that below):

• recipeCategory.id CONTAINS ALL ["category-id-1", "category-id-2"] AND tags.id IN ["tag-id-1", "tag-id-2", "tag-id-3"] AND tools.id IN ["tool-id-1"]

Which issue(s) this PR fixes:

(REQUIRED)

N/A

Special notes for your reviewer:

(fill-in or delete this section)

I always hated the workaround I did in #1508 and #1560 to get filters working for categories/tags/tools, but the existing parser couldn't handle joins (e.g. recipe.tag.id) and assumed all values were singular (rather than lists).

There were a few other parser challenges, but those were the two main ones. I fixed the joins in #2265 and fixed the remaining issues here.

Testing

(fill-in or delete this section)

I added a bunch of tests prior to the refactor, then more after the refactor. God bless tests.

Once this PR is accepted, there are two tasks that should be done sooner or later:

1. Deprecate the old category/tag/tool filter params I made because they're bad
2. Update the documentation to include examples with the new keywords

Release Notes

(REQUIRED)

improved the backend filter API to support additional SQL keywords