feat: repository enhancements and MySQL SQLAlchemy support

[cofin]

This PR adds the following additional features:

• adds support and tests for MySQL using the asyncmy drivers.
• Basic repository docs. A more comprehensive usage guide will be completed when the Service and DTO patterns have been merged
• get_or_create optionally accepts a match_fields argument. This lets you lookup a model using a subset of the kwargs you've provided. If the remaining kwargs are different from the retrieved model's stored values, an update is performed.
• Adds OrderBy and SearchFilter filter types. OrderBy appends the ORDER BY clause to a statement and SearchFilter adds WHERE LIKE .. clause. It optionally has a case insensitive override.
• Renamed base_select to statement.

PR Checklist

• Have you followed the guidelines in CONTRIBUTING.rst?
• Have you got 100% test coverage on new code?
• Have you updated the prose documentation?
• Have you updated the reference documentation?

[provinzkraut]

Since these database backed tests are quite slow, can we maybe add a pytest marker to skip them?

[Goldziher]

can we run the DB tests only on main? or maybe using a schedule (github action cron basically).

[provinzkraut]

can we run the DB tests only on main? or maybe using a schedule (github action cron basically).

Hmm. I think we generally do want to run those in our CI and locally (maybe optionally). It's not like they take ages to run (the asyncpg tests take 5 seconds once the container is set up). That's not too bad on its own, but if we start adding many other dbs, it will somewhat add up. For me, just having a marker to be able to skip them if I want would be good enough. For the CI, it definitely doesn't matter since we have steps that take significantly longer than our whole test suite.

[Goldziher]

can we run the DB tests only on main? or maybe using a schedule (github action cron basically).

Hmm. I think we generally do want to run those in our CI and locally (maybe optionally). It's not like they take ages to run (the asyncpg tests take 5 seconds once the container is set up). That's not too bad on its own, but if we start adding many other dbs, it will somewhat add up. For me, just having a marker to be able to skip them if I want would be good enough. For the CI, it definitely doesn't matter since we have steps that take significantly longer than our whole test suite.

ok

[provinzkraut]

@cofin is this currently blocked by something?

[cofin]

No, it's not blocked by anything, and I need to wrap this up. Based on the last status, I need to add the Pytest marker and merge the latest changes.

[provinzkraut]

No, it's not blocked by anything, and I need to wrap this up. Based on the last status, I need to add the Pytest marker and merge the latest changes.

Okay, cool, just checking in!

[cofin]

I've been having issues with the asyncmy library, and it looks like there's an existing issue that references the problem: long2ice/asyncmy#39

[cofin]

I've excluded these mysql tests by default. I can do the same with the asyncpg tests if that makes sense?

[peterschutt]

I've excluded these mysql tests by default. I can de the same with the asyncpg tests if that makes sense?

I.e., exclude from the general CI tests?