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

[moutonjeremy]

Potential fix for https://github.com/Labbs/fiber-oapi/security/code-scanning/1

To fix this issue, we need to add the permissions key to the workflow, either globally at the top level (to apply to all jobs) or within the specific job (build). Since the workflow only appears to require image read access for source code and use of artifacts, specifying contents: read at the top level is a good minimal starting point. This ensures restricted GITHUB_TOKEN permissions for all jobs unless overridden. Edit .github/workflows/pr.yaml to insert a permissions: block following the workflow name and preceding the on: section (recommended by GitHub documentation), like so:

name: Pull Request Pipeline
permissions:
  contents: read

No additional imports, method definitions or dependencies are needed; this is just YAML structure.

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 GitHub Actions workflow permissions. The change restricts the default GITHUB_TOKEN permissions to read-only access for repository contents, following the principle of least privilege.

Key Changes:

• Added explicit permissions configuration to the workflow with contents: read

---

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