K8SPS-417: add podDisruptionBudget support

[pooknull]

https://perconadev.atlassian.net/browse/K8SPS-417

DESCRIPTION

This PR adds the following sections to the cr.yaml:

• .spec.mysql.podDisruptionBudget
• .spec.proxy.haproxy.podDisruptionBudget
• .spec.proxy.router.podDisruptionBudget
• .spec.orchestrator.podDisruptionBudget

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

[hors]

@pooknull please add e2e test for it (we have some test for PXCO)

[egegunes]

@pooknull please check init-deploy test:

    case.go:396: failed in step 1-create-cluster
    case.go:398: poddisruptionbudgets.policy "init-deploy-haproxy" not found
    case.go:398: poddisruptionbudgets.policy "init-deploy-mysql" not found
    case.go:398: poddisruptionbudgets.policy "init-deploy-orchestrator" not found

[pooknull]

@egegunes init-deploy test fails because the crVersion: 0.11.0 is used

[egegunes]

@egegunes init-deploy test fails because the crVersion: 0.11.0 is used

are there any reasons to run init-deploy with 0.11.0?

[JNKPercona]

Test name	Status
version-service	passed
async-ignore-annotations	passed
auto-config	passed
config	passed
config-router	passed
demand-backup	passed
async-data-at-rest-encryption	passed
gr-data-at-rest-encryption	passed
gr-demand-backup	passed
gr-demand-backup-haproxy	passed
gr-finalizer	passed
gr-haproxy	passed
gr-ignore-annotations	passed
gr-init-deploy	passed
gr-one-pod	passed
gr-recreate	passed
gr-scaling	passed
gr-scheduled-backup	passed
gr-security-context	passed
gr-self-healing	passed
gr-tls-cert-manager	passed
gr-users	passed
haproxy	passed
init-deploy	passed
limits	passed
monitoring	passed
one-pod	passed
operator-self-healing	passed
recreate	passed
scaling	passed
scheduled-backup	passed
service-per-pod	passed
sidecars	passed
smart-update	passed
storage	passed
tls-cert-manager	passed
users	passed
pvc-resize	passed
We run 38 out of 38

commit: 449f149
image: perconalab/percona-server-mysql-operator:PR-991-449f149b