CLOUD-915: Add flags to disable monitoring and logging in PR job

[jvpasinatto]

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?
• Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

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

[JNKPercona]

Test Name	Result	Time
arbiter	failure	00:00:00
balancer	failure	00:00:00
cross-site-sharded	failure	00:00:00
custom-replset-name	failure	00:00:00
custom-tls	failure	00:00:00
custom-users-roles	failure	00:00:00
custom-users-roles-sharded	failure	00:00:00
data-at-rest-encryption	failure	00:00:00
data-sharded	failure	00:00:00
demand-backup	failure	00:00:00
demand-backup-eks-credentials-irsa	skipped	00:00:00
demand-backup-fs	skipped	00:00:00
demand-backup-incremental	skipped	00:00:00
demand-backup-incremental-sharded	skipped	00:00:00
demand-backup-physical-parallel	skipped	00:00:00
demand-backup-physical-aws	skipped	00:00:00
demand-backup-physical-azure	skipped	00:00:00
demand-backup-physical-gcp	skipped	00:00:00
demand-backup-physical-minio	skipped	00:00:00
demand-backup-physical-sharded-parallel	skipped	00:00:00
demand-backup-physical-sharded-aws	skipped	00:00:00
demand-backup-physical-sharded-azure	skipped	00:00:00
demand-backup-physical-sharded-gcp	skipped	00:00:00
demand-backup-physical-sharded-minio	skipped	00:00:00
demand-backup-sharded	skipped	00:00:00
expose-sharded	skipped	00:00:00
finalizer	skipped	00:00:00
ignore-labels-annotations	skipped	00:00:00
init-deploy	skipped	00:00:00
ldap	skipped	00:00:00
ldap-tls	skipped	00:00:00
limits	skipped	00:00:00
liveness	skipped	00:00:00
mongod-major-upgrade	skipped	00:00:00
mongod-major-upgrade-sharded	skipped	00:00:00
monitoring-2-0	skipped	00:00:00
monitoring-pmm3	skipped	00:00:00
multi-cluster-service	skipped	00:00:00
multi-storage	skipped	00:00:00
non-voting-and-hidden	skipped	00:00:00
one-pod	skipped	00:00:00
operator-self-healing-chaos	skipped	00:00:00
pitr	skipped	00:00:00
pitr-physical	skipped	00:00:00
pitr-sharded	skipped	00:00:00
pitr-physical-backup-source	skipped	00:00:00
preinit-updates	skipped	00:00:00
pvc-resize	skipped	00:00:00
recover-no-primary	skipped	00:00:00
replset-overrides	skipped	00:00:00
rs-shard-migration	skipped	00:00:00
scaling	skipped	00:00:00
scheduled-backup	skipped	00:00:00
security-context	skipped	00:00:00
self-healing-chaos	skipped	00:00:00
service-per-pod	skipped	00:00:00
serviceless-external-nodes	skipped	00:00:00
smart-update	skipped	00:00:00
split-horizon	skipped	00:00:00
stable-resource-version	skipped	00:00:00
storage	skipped	00:00:00
tls-issue-cert-manager	skipped	00:00:00
upgrade	skipped	00:00:00
upgrade-consistency	skipped	00:00:00
upgrade-consistency-sharded-tls	skipped	00:00:00
upgrade-sharded	skipped	00:00:00
users	skipped	00:00:00
version-service	skipped	00:00:00
We run 10 out of 68		N/A

commit: b55192f
image: perconalab/percona-server-mongodb-operator:PR-1993-b55192fa