[Flake] ScyllaDBMonitoring should setup monitoring stack [It] with "SaaS" monitoring type

[rzetelskik]

Link to the job that flaked.

https://prow.scylla-operator.scylladb.com/view/gs/scylla-operator-prow/pr-logs/pull/scylladb_scylla-operator/2339/pull-scylla-operator-master-e2e-gke-parallel-clusterip/1881294842714132480#1:test-build-log.txt%3A2437

Snippet of what failed.

[FAILED] Timed out after 600.001s.
  The function passed to Eventually failed at github.com/scylladb/scylla-operator/test/e2e/set/scylladbmonitoring/scylladbmonitoring.go:350 with:
  Unexpected error:
      <*url.Error | 0xc000a52510>: 
      Get "https://admin/:***@10.119.164.20:9142/api/search?limit=1000&page=1&type=dash-db": EOF
      {
          Op: "Get",
          URL: "https://admin/:***@10.119.164.20:9142/api/search?limit=1000&page=1&type=dash-db",
          Err: <*errors.errorString | 0x49bc800>{s: "EOF"},
      }
  occurred
  In [It] at: github.com/scylladb/scylla-operator/test/e2e/set/scylladbmonitoring/scylladbmonitoring.go:352 @ 01/20/25 11:31:24.66
  Full Stack Trace
    github.com/scylladb/scylla-operator/test/e2e/set/scylladbmonitoring.init.func2.2(0xc0004db780)
    	github.com/scylladb/scylla-operator/test/e2e/set/scylladbmonitoring/scylladbmonitoring.go:352 +0x21f9
    reflect.Value.call({0x1ef9000?, 0xc0003a2050?, 0xc000ac9ca0?}, {0x2440919, 0x4}, {0xc000f12870, 0x1, 0xc000f12870?})
    	reflect/value.go:581 +0xca6
    reflect.Value.Call({0x1ef9000?, 0xc0003a2050?, 0x363d730?}, {0xc000f12870?, 0x19f0445?, 0xc000c6be00?})
    	reflect/value.go:365 +0xb9

[scylla-operator-bot]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[scylla-operator-bot]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out

/lifecycle rotten