Update to Postgres driver version 42.7.7

[labkey-susanh]

Rationale

CVE-2025-49146 Affects versions from 42.7.4 until 42.7.7. We are not at risk since we do not configure channel binding, but good to update just the same.

Changes

• Update postgresDriverVersion

[labkey-jeckels]

Looks good, pending positive feedback from TeamCity.

[labkey-adam]

@labkey-susanh @labkey-jeckels As mentioned in the "Upgrade Dependencies" doc, we've been holding off upgrading the PG JDBC driver due to a metadata retrieval performance issue that @labkey-tchad filed. Doesn't look like that's been fixed... or has it? Are we okay upgrading with this degradation in place?

[labkey-susanh]

@labkey-susanh @labkey-jeckels As mentioned in the "Upgrade Dependencies" doc, we've been holding off upgrading the PG JDBC driver due to a metadata retrieval performance issue that @labkey-tchad filed. Doesn't look like that's been fixed... or has it? Are we okay upgrading with this degradation in place?

Thanks, @labkey-adam. I didn't realize/remember that this was a thing. I think we're probably safe to suppress this CVE since it's related to functionality that we do not use. Anyone disagree?

[labkey-jeckels]

@labkey-susanh @labkey-jeckels As mentioned in the "Upgrade Dependencies" doc, we've been holding off upgrading the PG JDBC driver due to a metadata retrieval performance issue that @labkey-tchad filed. Doesn't look like that's been fixed... or has it? Are we okay upgrading with this degradation in place?

Thanks, @labkey-adam. I didn't realize/remember that this was a thing. I think we're probably safe to suppress this CVE since it's related to functionality that we do not use. Anyone disagree?

Sounds correct to me.