CLOUD-881: Use release_versions in Makefile release rule

[jvpasinatto]

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?
• Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

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 PXC version?
• Does the change support oldest and newest supported Kubernetes version?

[JNKPercona]

Test name	Status
affinity-8-0	failure
auto-tuning-8-0	failure
cross-site-8-0	failure
custom-users-8-0	failure
demand-backup-cloud-8-0	failure
demand-backup-encrypted-with-tls-8-0	failure
demand-backup-8-0	failure
haproxy-5-7	failure
haproxy-8-0	failure
init-deploy-5-7	failure
init-deploy-8-0	failure
limits-8-0	failure
monitoring-2-0-8-0	failure
one-pod-5-7	failure
one-pod-8-0	failure
pitr-8-0	failure
pitr-gap-errors-8-0	failure
proxy-protocol-8-0	failure
proxysql-sidecar-res-limits-8-0	failure
pvc-resize-5-7	failure
pvc-resize-8-0	failure
recreate-8-0	failure
restore-to-encrypted-cluster-8-0	failure
scaling-proxysql-8-0	failure
scaling-8-0	failure
scheduled-backup-5-7	failure
scheduled-backup-8-0	failure
security-context-8-0	failure
smart-update1-8-0	failure
smart-update2-8-0	failure
storage-8-0	failure
tls-issue-cert-manager-ref-8-0	failure
tls-issue-cert-manager-8-0	failure
tls-issue-self-8-0	failure
upgrade-consistency-8-0	failure
upgrade-haproxy-5-7	failure
upgrade-haproxy-8-0	failure
upgrade-proxysql-5-7	failure
upgrade-proxysql-8-0	failure
users-5-7	failure
users-8-0	failure
validation-hook-8-0	failure
We run 42 out of 42

commit: eb2aea2
image: perconalab/percona-xtradb-cluster-operator:PR-1936-eb2aea2b