[BUG] [v2.0] PostgreSQL yum repo GPG key not available

[przemyslavic]

Describe the bug
PostgreSQL yum repository GPG key is no longer uvailable under the following url:
https://download.postgresql.org/pub/repos/yum/RPM-GPG-KEY-PGDG

2024-01-08 01:16:23,329 [INFO]: Adding third party repositories...
2024-01-08 01:16:45,868 [WARNING]: curl: (22) The requested URL returned error: 404 ", "error: https://download.postgresql.org/pub/repos/yum/RPM-GPG-KEY-PGDG: import read failed(2)."
2024-01-08 01:16:46,310 [WARNING]: curl: (22) The requested URL returned error: 404 ", "error: https://download.postgresql.org/pub/repos/yum/RPM-GPG-KEY-PGDG: import read failed(2)."
2024-01-08 01:16:46,563 [WARNING]: curl: (22) The requested URL returned error: 404 ", "error: https://download.postgresql.org/pub/repos/yum/RPM-GPG-KEY-PGDG: import read failed(2)."
2024-01-08 01:16:46,563 [WARNING]: Retries count reached maximum, command: `rpm --import https://download.postgresql.org/pub/repos/yum/RPM-GPG-KEY-PGDG`"
2024-01-08 01:16:46,563 [ERROR]: No alternatives available, exiting...

How to reproduce
Steps to reproduce the behavior:

1. execute epicli apply to deploy an RHEL/AlmaLinux cluster with PostgreSQL component enabled
   The installation will fail on repository setup trying to import GPG key for PostgreSQL yum repo.

Expected behavior
The cluster should be deployed without any issues.

Config files
If applicable, add config files to help explain your problem.

Environment

• Cloud provider: [all]
• OS: [RHEL, AlmaLinux]

epicli version: [v2.0]

Additional context
Add any other context about the problem here.

---

DoD checklist

• Changelog
  • updated
  • not needed
• COMPONENTS.md
  • updated
  • not needed
• Schema
  • updated
  • not needed
• Backport tasks
  • created
  • not needed
• Documentation
  • added
  • updated
  • not needed
• Feature has automated tests
• Automated tests passed (QA pipelines)
  • apply
  • upgrade
  • backup/restore
• Idempotency tested
• All conversations in PR resolved