feat: Update supported PostgreSQL versions

[susnux]

• Requires feat: Add postgres 17 docker-ci#680
• Resolves Support PostgreSQL 17 #48495
• Documentation: feat: Support postgres 17 but drop postgres 12 documentation#12363

Summary

12 is now EOL but 17 was released and should be supported and tested.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[nickvergessen]

Btw I use MySQL 9.x since many months without an issue :D

[nickvergessen]

CI fails :P

[susnux]

I use MySQL 9.x since many months without an issue :D

They have so short lifespan, I would wait for 9.7 lts. Otherwise we need to update the workflows regularly, no?

[nickvergessen]

I was more talking about the warning in the setup check.
Doctrine is also testing against the latest 9.x:
https://github.com/doctrine/dbal/blob/4.2.x/.github/workflows/continuous-integration.yml#L375

So I guess it would be nice to add it.

• 9.0 was released in July https://dev.mysql.com/doc/relnotes/mysql/9.0/en/
• 9.1 was released in October https://dev.mysql.com/doc/relnotes/mysql/9.1/en/

So ~once per our major. Sounds good enough?

[susnux]

So ~once per our major. Sounds good enough?

Well, yes that makes sense. So we can spot issues early.
But would you also add this to the setup check?

[wrenix]

"backport requested" is checked but i do not see any backport

[susnux]

"backport requested" is checked but i do not see any backport

Just means backports are requested if needed. We do not backport features so there is no backport.