Sync swagger: flatten consumption trace filter to repeated span filters

CHANGELOG.md

@@ -2,6 +2,15 @@
 
 ## Unreleased
 
+### Added
+* Add `PARENT_SERVICE`, `PARENT_OPERATION`, `ROOT_SERVICE`, and `ROOT_OPERATION` group-by key types to `v1/config/TraceMetricsRules`.
+
+### Changed
+* Replace the `trace_filter` field on `v1/config/ConsumptionConfig` partition filter conditions with a repeated `trace_span_filters` field: a list of `ConsumptionSpanFilter` carried directly on the condition (the previous `ConsumptionTraceFilter` wrapper is gone). Matching happens at the span level: a span matches the condition only if it satisfies every span filter in the list (match alternatives with an `IN` string filter or with separate conditions). This field is in preview and gated by the `enable-consumption-trace-api` feature flag. (The previous shape was never operative: the field has always been gated by the `enable-consumption-trace-api` flag, which was never enabled for any customer tenant while the old shape existed, so no existing manifest is affected.) Manifests containing the new `trace_span_filters` shape require this release or newer; older chronoctl versions reject them at decode and render the filter as empty when reading entities.
+
+### Removed
+* Remove the deprecated `sku_group` field from `v1/config/ConsumptionBudget` thresholds in favor of `resource_group`. **This is a breaking change**.
+
 ## v1.28.0
 
 ### Added