dependency on retired package, `databases`

[onerandomusername]

Looks like @encode recently retired the databases library, which ormar uses internally. It would be beneficial to either migrate, or perhaps begin maintaining databases in conjunction with a transfer from encode.

Just posting this here so there are eyes, I was looking to perhaps use ormar again, but this is a dealbreaker as it stands, while the future is up in the air.

[pmdevita]

There was some conversation about this in the SQLAlchemy 2 PR #1269 I think we already have approval from collerek to remove it and I started an attempt to do so, the hardest part I think is we have to completely reimplement transactions since we relied on databases for that.

[collerek]

Yeah - for now I updated the databases to the latest version, but for the future it needs to be removed. As @pmdevita mentioned, we need to work on transactions and also check the caching of sqlalchemy to mitigate the performance drop.

[collerek]

Dropped databases in 0.22.0