Cardinality capping is a relatively difficult topic to understand. A lot of users make incorrect assumptions about the topic. To make life easier, we need to write a full tutorial explaining the concept, and how OTel's approach to reporting overflow can be (and should be) used by users when querying metrics.

I plan to use Aspire dashboard tool for the tutorial, as that is the only OpenSource tool that natively understand's Otel's overflow attribute.
dotnet/aspire#7784

Topics to cover:

1. What is cardinality limit?
2. How OTel enforces the limit?
3. What attributes are subject to the cap (more importantly, what is not subject to cap)
4. How users should plan for cardinality limit?
5. How delta vs cumulative influences cardinality limit.
6. How to leverage overflow signal, to avoid making incorrect decisions based on Metric data. (Most important!)