K8SPG-543: fix panic

[pooknull]

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

DESCRIPTION

Problem:
Applying a cr.yaml with empty .spec.proxy field caused operator to panic.

Solution:
Set correct defaults.

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 the manifests (crd/bundle) regenerated if needed?
• 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	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
telemetry-transfer	passed
upgrade-minor	passed
users	passed
We run 12 out of 12

commit: 58719fd
image: perconalab/percona-postgresql-operator:PR-708-58719fddd