Forward connection pool parameters from django to psycopg

[ticosax]

Django allows to customize the connection pool through the app settings.
Why not forwarding them to the connection worker for sake of consistency ?

Useful when we want to cap the max_size, as an example.

Not sure how we want to advertise this change in the documentation ?
Maybe the changelog is enough ?
Maybe it's a breaking change if users, suddenly, end up with a connection pool not optimized for the workers.

⚠️ Only psycopg is supported, as I don't think using django + aiopg is a thing. I could be wrong though.

Successful PR Checklist:

• Tests
  • (not applicable?)
• Documentation
  • (not applicable?)

PR label(s):

• PR type: breaking 💥 Contains breaking changes
• PR type: feature ⭐️ Contains new features
• PR type: bugfix 🕵️ Contains bug fix
• PR type: miscellaneous 👾 Contains misc changes
• PR type: dependencies 🤖 Contains only dependencies updates
• PR type: documentation 📚 Contains documentation updates

[ewjoachim]

Cool :) I'm seeing some tests fail ?

I'm really sorry that it took so long to review. My energy for doing reviews on my spare time is scarce these days 😅 . Your contribution is appreciated though.

I don't think using django + aiopg is a thing

No it's not, what you did makes sense. Also... I'm considering dropping non-psycopg3 so as to reduce maintenance burden.