ci: declare workflow-level contents: read on 3 workflows

Pins the default GITHUB_TOKEN to contents: read on workflows that don't
call a GitHub API beyond the initial checkout. Other workflows that need
write scopes are left implicit for a maintainer to declare.

Motivation: CVE-2025-30066 (March 2025 tj-actions/changed-files
compromise) exfiltrated GITHUB_TOKEN from workflow logs. Per-workflow
caps bound runtime authority irrespective of repo or org default,
give drift protection, and are credited per-file by the OpenSSF
Scorecard Token-Permissions check.

YAML validated locally with yaml.safe_load.

Signed-off-by: Arpit Jain <arpitjain099@gmail.com>

Author: arpitjain099

.github/workflows/ci-package-manager.yml

@@ -9,6 +9,9 @@ on:
         branches:
             - main
 
+permissions:
+  contents: read
+
 jobs:
     ci-package-manager:
         uses: eslint/workflows/.github/workflows/ci-package-manager.yml@main

.github/workflows/ci.yml

@@ -6,6 +6,10 @@ on:
     pull_request:
         branches:
             - main
+
+permissions:
+  contents: read
+
 jobs:
     lint:
         name: Lint

.github/workflows/update-readme.yml

@@ -6,6 +6,9 @@ on:
 
     workflow_dispatch:
 
+permissions:
+  contents: read
+
 jobs:
     update-readme:
         uses: eslint/workflows/.github/workflows/update-readme.yml@main