Update CI

[seuros]

Those version are outdated and EOL.

For Mysql there is version 8.5 , but 8 is fine.

For postgresql, we use latest so we can try all the new features that don't exist in the past.

[enebo]

@seuros seems reasonable to me. If we find some issue with older postgresql that is still supported by 8.0 then we can either bump it back or add another service later.

[seuros]

I’ve gone through the PostgreSQL adapter line by line, even built extensions like PostGIS on top of it. Unless you're relying on some non-native extension, nothing breaks. It’s stable, predictable, and professionally maintained.

MySQL? Feels like a student project. They sneak in undocumented breaking changes, like in a event we had in with_advisory_lock, where version 5.7.5 silently stopped supporting nested locks without even a version bump. No heads-up, no clear fix. Just vibes.

They also randomly switched default authentication methods in some obscure release in version 8, which broke the Trilogy adapter for months, not even sure if that was fixed.

[seuros]

@enebo

The client had to be updated . I will remove that usage eventually later.