K8SPG-894 upgrade job using the init container from primary sts

[gkech]

CHANGE DESCRIPTION

Problem:

The major upgrade fails if the custom extensions are enabled with error:

  Warning  Failed     10m   kubelet            Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/opt/crunchy/bin/relocate-extensions.sh": stat /opt/crunchy/bin/relocate-extensions.sh: no such file or directory: unknown

The error is connected with changing /relocate-extensions.sh to CRUNCHY_BINDIR percona-postgresql-operator/percona/extensions/containers.go at 347501a9072afa4d8366099fc31b37af90afb158 · percona/percona-postgresql-operator

The solution is to run the database-init init container as part of the upgrade job. It should also be the first container to be executed from the set of init containers cause subsequent init-containers may require scripts that were installed by it e.g. custom extensions.

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?