Change link checking from markdown-link-check to lychee

.github/workflows/reusable-markdown-link-check.yml

@@ -9,13 +9,13 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Install markdown-link-check
-        # TODO(jack-berg): use latest when config file reading bug is fixed: https://github.com/tcort/markdown-link-check/issues/246
-        run: npm install -g [email protected]
-
-      - name: Run markdown-link-check
-        run: |
-          find . -type f \
-                 -name '*.md' \
-                 -not -path './CHANGELOG.md' \
-               | xargs .github/scripts/markdown-link-check-with-retry.sh
+      - uses: lycheeverse/lychee-action@v2
+        with:
+          # remove version after next release of lychee-action
+          lycheeVersion: latest
+          # excluding links to pull requests and issues is done for performance
+          args: >
+            --include-fragments
+            --exclude "^https://github.com/open-telemetry/opentelemetry-java-contrib/(issue|pull)/\\d+$"
+            --max-retries 6
+            .

jfr-events/README.md

@@ -1,7 +1,5 @@
 # OpenTelemetry Java Flight Recorder (JFR) Events
 
-[![Javadocs][javadoc-image]][javadoc-url]
-
 Create JFR events that can be recorded and viewed in Java Mission Control (JMC).
 
 * Creates Open Telemetry Tracing/Span events for spans
@@ -20,9 +18,6 @@ Create JFR events that can be recorded and viewed in Java Mission Control (JMC).
 * Supports the Open Source version of JFR in Java 11.
   * Might support back port to OpenJDK 8, but not tested and classes are built with JDK 11 bytecode.
 
-[javadoc-image]: https://www.javadoc.io/badge/io.opentelemetry/opentelemetry-sdk-extension-jfr-events.svg
-[javadoc-url]: https://www.javadoc.io/doc/io.opentelemetry/opentelemetry-sdk-extension-jfr-events
-
 ## Component owners
 
 - [Staffan Friberg](https://github.com/sfriberg)

noop-api/README.md

@@ -1,7 +1,5 @@
 # OpenTelemetry Noop API
 
-[![Javadocs][javadoc-image]][javadoc-url]
-
 An implementation of `OpenTelemetry` that is completely no-op. Unlike `OpenTelemetry#noop()`, this
 implementation does not support in-process context propagation at all. This means that no objects
 are allocated nor {@link ThreadLocal}s used in an application using this implementation.
@@ -11,6 +9,3 @@ are allocated nor {@link ThreadLocal}s used in an application using this impleme
 - [Jack Berg](https://github.com/jack-berg), New Relic
 
 Learn more about component owners in [component_owners.yml](../.github/component_owners.yml).
-
-[javadoc-image]: https://www.javadoc.io/badge/io.opentelemetry/opentelemetry-extension-noop-api.svg
-[javadoc-url]: https://www.javadoc.io/doc/io.opentelemetry/opentelemetry-extension-noop-api