CLOUD-881: Use release_versions in Makefile release rule

[ptankov]

CHANGE DESCRIPTION

Problem:
The "release" rule was not fully automated, requiring manual replacement of images in the release process.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
The Makefile rule release can be improved by using the images present in release_versions file, eliminating the manual replacement of the images names.

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?
• Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
• Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

• Is an E2E test/test case added for the new feature/change?
• Are unit tests added where appropriate?

Config/Logging/Testability

• Are all needed new/changed options added to default YAML files?
• Are all needed new/changed options added to the Helm Chart?
• Did we add proper logging messages for operator actions?
• Did we ensure compatibility with the previous version or cluster upgrade process?
• Does the change support oldest and newest supported PG version?
• Does the change support oldest and newest supported Kubernetes version?

[JNKPercona]

Test name	Status
custom-extensions	failure
custom-tls	failure
demand-backup	failure
finalizers	failure
init-deploy	failure
monitoring	failure
one-pod	failure
operator-self-healing	failure
pitr	failure
scaling	failure
scheduled-backup	failure
self-healing	failure
sidecars	failure
start-from-backup	failure
tablespaces	failure
telemetry-transfer	failure
upgrade-consistency	failure
upgrade-minor	failure
users	failure
We run 19 out of 19

commit: ca15afa
image: perconalab/percona-postgresql-operator:PR-1037-ca15afa78