K8SPG-613: use percona-pgbackrest image

[pooknull]

https://perconadev.atlassian.net/browse/K8SPG-613

CHANGE DESCRIPTION

Problem:
Short explanation of the problem.

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

Solution:
Short explanation of the solution we are providing with this PR.

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?

[github-actions]

[gofmt] _{reported by reviewdog 🐶}

Suggested change

	if err := r.generateRestoreJobIntent(cluster, configHash, instanceName, cmd,
	if err := r.generateRestoreJobIntent(cluster, configHash, instanceName, cmd,

[hors]

maybe better to use percona-bin

[JNKPercona]

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

commit: 2859269
image: perconalab/percona-postgresql-operator:PR-1098-2859269f5