Potential fix for code scanning alert no. 63: Workflow does not contain permissions

[AlexJSully]

Potential fix for https://github.com/AlexJSully/Small-Dev-Talk/security/code-scanning/63

To fix the problem, add an explicit permissions block to the workflow or the job to limit the permissions of the GITHUB_TOKEN to the minimum necessary. Since this Markdown lint job does not need any write access to the repository, you should add permissions: contents: read as either a top-level key (applies to all jobs) or at the job level. Since there is only one job, both approaches work, but top-level is preferable for simplicity and is the most common practice. Edit .github/workflows/markdown-lint.yaml to insert the following after the name: line and before on: (i.e., after line 1).

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[Copilot]

Pull Request Overview

This PR addresses a security code scanning alert by adding explicit permissions to the GitHub Actions workflow to limit the GITHUB_TOKEN scope to the minimum necessary permissions.

• Adds a top-level permissions block with contents: read to restrict the workflow's token permissions
• Follows security best practices by implementing the principle of least privilege for GitHub Actions

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}