Clarify that attribute requirement levels apply to instrumentation li…

…braries (#3289)

Based on discussion in semconv stability WG

Closes #3283

## Changes

Clarifies that attribute requirement levels apply to instrumentation.
And that, because users can transform their telemetry in a number of
ways (e.g. metric views, span processors, and collector
transformations), these requirement levels cannot be relied on by
telemetry consumers.

---------

Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com>

CHANGELOG.md

@@ -22,6 +22,8 @@ release.
 
 ### Semantic Conventions
 
+- Clarify that attribute requirement levels apply to the instrumentation library
+  ([#3289](https://github.com/open-telemetry/opentelemetry-specification/pull/3289))
 - Fix grammatical number of metric units.
   ([#3298](https://github.com/open-telemetry/opentelemetry-specification/pull/3298))
 - Rename `net.app.protocol.(name|version)` to `net.protocol.(name|version)`

specification/common/attribute-requirement-level.md

@@ -19,6 +19,8 @@
 
 _This section applies to Log, Metric, Resource, and Span, and describes requirement levels for attributes defined in semantic conventions._
 
+Attribute requirement levels apply to the [instrumentation library](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md#instrumentation-library).
+
 The following attribute requirement levels are specified:
 
 - [Required](#required)