Upgrading postgres client library to postgresql13-client

[vivekshankar1]

Signed-off-by: Vivek Shankar vshankar@progress.com

🔩 Description: What code changed, and why?

Due to issues with Backup failure on postgresql13 version we needed the client library to be upgraded in automate

⛓️ Related Resources

#6490 6490

👍 Definition of Done

👟 How to Build and Test the Change

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

[netlify]

👷 Deploy Preview for chef-automate processing.

🔨 Explore the source changes: 6574f94

🔍 Inspect the deploy log: https://app.netlify.com/sites/chef-automate/deploys/61cdaa0ac8ffb800087ee7d0

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
35.3% Duplication