ci: harden workflow token permissions

[arpitjain099]

This narrows the GITHUB_TOKEN for .github/workflows/check.yml, .github/workflows/lint.yml, .github/workflows/test.yml to read-only.

• These jobs only check out the repo and run build/test steps, so contents: read covers them.
• Without an explicit block the token inherits the repo default, often write-enabled.
• Following the principle of least privilege from the GitHub Actions security hardening guide.

Behavior is unchanged.

[vercel]

@arpitjain099 is attempting to deploy a commit to the Svelte Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c34d93b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[arpitjain099]

Consolidating to avoid a duplicate: #213 already declares the same read-only permissions on these workflow(s) (and others), so I'm closing this one in its favor. Apologies for the overlap.