Mark cardinality limits as Stable (open-telemetry#4222)

CHANGELOG.md

@@ -26,6 +26,8 @@ release.
   ([#4161](https://github.com/open-telemetry/opentelemetry-specification/pull/4161))
 - Clarify that applying cardinality limits should be done after attribute filtering.
   ([#4228](https://github.com/open-telemetry/opentelemetry-specification/pull/4228))
+- Mark cardinality limits as stable.
+  ([#4222](https://github.com/open-telemetry/opentelemetry-specification/pull/4222))
 
 ### Logs
 

specification/metrics/sdk.md

@@ -399,8 +399,7 @@ The SDK MUST accept the following stream configuration parameters:
   If the user does not provide an `exemplar_reservoir` value, the
   `MeterProvider` MUST apply a [default exemplar
   reservoir](#exemplar-defaults).
-* **Status**: [Development](../document-status.md) -
-  `aggregation_cardinality_limit`: A positive integer value defining the
+* `aggregation_cardinality_limit`: A positive integer value defining the
   maximum number of data points allowed to be emitted in a collection cycle by
   a single instrument. See [cardinality limits](#cardinality-limits), below.
 
@@ -774,7 +773,7 @@ of metrics across successive collections.
 
 ### Cardinality limits
 
-**Status**: [Development](../document-status.md)
+**Status**: [Stable](../document-status.md)
 
 SDKs SHOULD support being configured with a cardinality limit. The number of
 unique combinations of attributes is called cardinality. For a given metric, the