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

[jvpasinatto]

CHANGE DESCRIPTION

Problem:
GKE cluster were being created with logging and monitoring by default, but we don't need it for this job.

Solution:
Add flags to disable them. Also fix test report that was missing timing information.

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?

[JNKPercona]

Test Name	Result	Time
backup-enable-disable	passed	00:07:03
custom-extensions	passed	00:08:35
custom-tls	passed	00:05:58
demand-backup	passed	00:24:49
finalizers	passed	00:03:37
init-deploy	passed	00:03:25
monitoring	passed	00:07:21
monitoring-pmm3	passed	00:07:54
one-pod	passed	00:08:19
operator-self-healing	passed	00:07:52
pitr	passed	00:13:06
scaling	passed	00:04:53
scheduled-backup	passed	00:25:39
self-healing	passed	00:09:14
sidecars	passed	00:03:30
start-from-backup	passed	00:12:09
tablespaces	passed	00:07:59
telemetry-transfer	passed	00:03:11
upgrade-consistency	passed	00:06:50
upgrade-minor	passed	00:05:22
users	passed	00:03:45
We run 21 out of 21		03:00:43

commit: 5bdd599
image: perconalab/percona-postgresql-operator:PR-1187-5bdd59981