Commit 954fdbd

All central tenants share the store's disk and retention with tenant-root, and nothing reserves space per tenant. Every traces store is bounded by disk usage: without `retentionDiskUsageBytes` it drops its oldest day once its volume is 80% full. VictoriaTraces always keeps the last two days, though, so the disk cap alone does not stop a fast writer from filling the volume. Each tenant is therefore also held to a write rate, which the platform sets with `monitoring.tracingCentralTenantBytesPerSecond` in the platform package. By default it is about 97 KiB/s, at which one tenant alone cannot fill the disk cap of a default 10Gi store within two days, so raise it with the store. A change reaches every tenant's collector through the `cozystack-values` Secret, and upgrades every release in every tenant once. Each tenant's collector enforces it and refuses data above it. An OTLP/HTTP exporter gets a 429 and retries; an OTLP/gRPC exporter gets `RESOURCE_EXHAUSTED` without the `RetryInfo` the OTLP specification requires for a retry, so it drops those spans. Applications of central tenants should therefore export over HTTP. Several tenants writing at their limits together can still exceed the cap, so size the volume for the tenants you admit.