Revert "style: Enable Markdownlint rule max-one-sentence-per-line"

This reverts commit ff6a5be.

The max-one-sentence-per-line rule fragments explanatory content into
choppy, disconnected lines that harm readability. Technical documentation
often requires flowing prose to explain complex concepts coherently.
Removing this rule allows authors to write natural paragraphs that
maintain context and guide readers through detailed explanations

Signed-off-by: Thomas Steenbergen <opensource@steenbe.nl>

Author: tsteenbe

.github/workflows/static-analysis.yml

@@ -92,12 +92,8 @@ jobs:
         uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6
         with:
           fetch-depth: 0
-      - name: Setup Node
-        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6
       - name: Check for Markdown issues
-        run: |
-          npm install -g markdownlint-rule-max-one-sentence-per-line@0.0.2
-          npx markdownlint-cli2
+        uses: DavidAnson/markdownlint-cli2-action@07035fd053f7be764496c0f8d8f9f41f98305101 # v22
   prettier-website:
     runs-on: ubuntu-24.04
     steps:

.markdownlint-cli2.yaml

@@ -1,8 +1,6 @@
 #  Configuration for the markdownlint-cli2, see:
 #  https://github.com/DavidAnson/markdownlint-cli2/blob/main/test/markdownlint-cli2-yaml-example/.markdownlint-cli2.yaml
 
-customRules:
-  - markdownlint-rule-max-one-sentence-per-line
 globs:
   - "**/*.md"
 ignores: