RE-2169: chore: bump postgres client from 15 to 16

[erikburt]

Updating postgres client from 15 -> 16.

Copied changes from dc6bd0cbc27178a6146080cddbc14dd3d8a88f21, however there exist more places which reference postgres now. For example:

• https://github.com/smartcontractkit/chainlink/blob/dc9a073ab7e67a66eed49dd74e6ac0da1787b24c/plugins/chainlink.Dockerfile#L55
  • ~~This wasn't included in this PR because it doesn't reference 15 like the rest. It seems like it was either accidentally missed or purposefully excluded during the last bump~~

[github-actions[bot]]

I see that you haven't updated any CHANGELOG files. Would it make sense to do so?

[jmank88]

You can update plugins/chainlink.Dockerfile too - it was just overlooked. I probably created the PR before the others were bumped and missed it in a rebase.

[cl-sonarqube-production[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[github-actions[bot]]

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production[bot]]

Quality Gate failed

Failed conditions
3 Security Hotspots

See analysis details on SonarQube