chore(deps): bump davidanson/markdownlint-cli2-action action to v22 (#6760)

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Piotr Kiełkowicz <[email protected]>

Author: renovate[bot]

.github/workflows/markdownlint.yml

@@ -17,7 +17,7 @@ jobs:
       uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
     - name: run markdownlint
-      uses: DavidAnson/markdownlint-cli2-action@30a0e04f1870d58f8d717450cc6134995f993c63 # v21.0.0
+      uses: DavidAnson/markdownlint-cli2-action@07035fd053f7be764496c0f8d8f9f41f98305101 # v22.0.0
       with:
         globs: |
           **/*.md

README.md

@@ -48,8 +48,8 @@ files.
 > Certain components, marked as
 [pre-release](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/VERSIONING.md#pre-releases),
 are still work in progress and can undergo breaking changes before stable
-release. Check the individual `README.md` file for each component to understand its
-current state.
+release. Check the individual `README.md` file for each component to understand
+its current state.
 
 To understand which portions of the [OpenTelemetry
 Specification](https://github.com/open-telemetry/opentelemetry-specification)

docs/trace/links-based-sampler/README.md

@@ -42,8 +42,8 @@ scenario. Let's say we have a producer activity (say with ID S1 in Trace T1) tha
 produces a message and a consumer activity (say with ID S2 in Trace T2)  that
 consumes the message.
 
-Now, let's say that the producing activity S1 in trace T1 is sampled, say using the
-decision of a parent based sampler. Now, let's say that the activity S2 in trace
+Now, let's say that the producing activity S1 in trace T1 is sampled, say using
+the decision of a parent based sampler. Now, let's say that the activity S2 in trace
 T2 is not sampled based on the parent based sampler decision for T2. However,
 since this activity S2 in T2 is linked to the producing activity (S1 in T1) that
 is sampled, this mechanism ensures that the consuming activity (S2 in T2) will

src/OpenTelemetry.Exporter.Console/README.md

@@ -10,8 +10,8 @@ ConsoleExporter supports exporting logs, metrics and traces.
 > This exporter is intended for debugging and learning purposes. It is not
   recommended for production use. The output format is not standardized and can
   change at any time.
-  If a standardized format for exporting telemetry to stdout is desired, upvote on
-  [this feature request](https://github.com/open-telemetry/opentelemetry-dotnet/issues/5920).
+  If a standardized format for exporting telemetry to stdout is desired, upvote
+  on [this feature request](https://github.com/open-telemetry/opentelemetry-dotnet/issues/5920).
 
 ## Installation
 

src/OpenTelemetry.Exporter.OpenTelemetryProtocol/CHANGELOG.md

@@ -362,8 +362,8 @@ attributes will be exported when
 variable will be set to `true`.
 
   **NOTE**: These attributes were removed in [1.6.0-rc.1](#160-rc1) release in
-  order to support stable release of OTLP Log Exporter. The attributes will now be
-  available via environment variable mentioned above.
+  order to support stable release of OTLP Log Exporter. The attributes will now
+  be available via environment variable mentioned above.
   ([#4892](https://github.com/open-telemetry/opentelemetry-dotnet/pull/4892))
 
 * Added ability to export attributes corresponding to `LogRecord.EventId.Id` as

src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md

@@ -24,7 +24,8 @@ to scrape.
 > This exporter does not support Exemplars. For using Exemplars, use the [OTLP
 Exporter](../OpenTelemetry.Exporter.OpenTelemetryProtocol/README.md) and use a
 component like OTel Collector to expose metrics (with exemplars) to Prometheus.
-This [tutorial](../../docs/metrics/exemplars/README.md) shows one way how to do that.
+This [tutorial](../../docs/metrics/exemplars/README.md) shows one way how to do
+that.
 
 ## Prerequisite
 

src/OpenTelemetry.Exporter.Zipkin/CHANGELOG.md

@@ -6,9 +6,9 @@ Notes](../../RELEASENOTES.md).
 
 ## Unreleased
 
-* This package is deprecated and it will stop receiving any updates in December 2026.
-  Zipkin already supports OTLP ingestion. Change your exporter to
-  `OpenTelemetry.Exporter.OpenTelemetryProtocol` as stated in the
+* This package is deprecated and it will stop receiving any updates in
+  December 2026. Zipkin already supports OTLP ingestion. Change your exporter
+  to `OpenTelemetry.Exporter.OpenTelemetryProtocol` as stated in the
   [Deprecating Zipkin Exporter blog post](https://opentelemetry.io/blog/2025/deprecating-zipkin-exporters/).
   ([#6750](https://github.com/open-telemetry/opentelemetry-dotnet/pull/6750))
 
@@ -124,8 +124,9 @@ Released 2024-Apr-02
 
 Released 2024-Mar-27
 
-* Zipkin tags used for Instrumentation Library changed from `otel.library.name` and
-  `otel.library.version` to `otel.scope.name` and `otel.scope.version` respectively.
+* Zipkin tags used for Instrumentation Library changed from `otel.library.name`
+  and `otel.library.version` to `otel.scope.name` and `otel.scope.version`
+  respectively.
   Old versions of attributes are deprecated, but still exported
   for [backward compatibility](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.31.0/specification/common/mapping-to-non-otlp.md#instrumentationscope).
   ([#5473](https://github.com/open-telemetry/opentelemetry-dotnet/pull/5473))