f3s/monitoring: disable grafana, loki, tempo; reduce alloy to no-opHEADmaster

Grafana's SQLite-on-NFS persistence is unreliable across restarts (the
new pod can't reacquire a clean exclusive lock after any NFS bounce),
and with Loki + Tempo also gone there's nothing left for it to
visualize. Keeping Prometheus alone for metrics + alerting.

Changes:
- prometheus.yaml: add grafana.enabled=false in the kube-prometheus-stack
  values so the subchart no longer renders the grafana deployment/pvc.
- loki.yaml, tempo.yaml, grafana-ingress.yaml: renamed to .disabled
  (same pattern as commit 03a18c6) so 'kubectl apply -f argocd-apps/'
  stops re-creating them; the cluster Applications were also deleted,
  which cascade-removes the helm resources via the resources-finalizer.
- alloy.yaml: drop the loki.write and otelcol.* blocks (no destinations
  to ship to). DaemonSet stays deployed with a minimal 'logging' block
  so the chart can be re-enabled by restoring the blocks here.

Prometheus TSDB was also wiped (corrupted zero-byte WAL segments from
the same NFS blip that took grafana down) — done separately, not part
of this commit.

0 files changed, 0 insertions, 0 deletions