K8SPG-559: fix `.status.backupType`

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

DESCRIPTION

Problem: The initial replica-create backup is incorrectly identified as incremental in the .status.backupType field.

Cause: The backup type is currently determined by parsing the --flag option in the backup job's COMMAND_OPTS environment. If this flag is not found, the backup type defaults to incremental. However, the replica-create backup job does not include this flag.

Solution: The operator should obtain the backup type from the pgbackrest info command.

CHECKLIST

Jira

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

Tests

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

Config/Logging/Testability

[x] Are all needed new/changed options added to default YAML files?
[x] Are the manifests (crd/bundle) regenerated if needed?
[x] Did we add proper logging messages for operator actions?
[x] Did we ensure compatibility with the previous version or cluster upgrade process?
[x] Does the change support oldest and newest supported PG version?
[x] Does the change support oldest and newest supported Kubernetes version?

Test name	Status
custom-extensions	passed
demand-backup	passed
init-deploy	passed
monitoring	passed
operator-self-healing	passed
scaling	passed
scheduled-backup	passed
self-healing	passed
start-from-backup	passed
tablespaces	passed
telemetry-transfer	passed
upgrade-minor	passed
users	passed
We run 13 out of 13

percona / percona-postgresql-operator

K8SPG-559: fix `.status.backupType` #762

DESCRIPTION

CHECKLIST