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

[edinc]

Potential fix for https://github.com/edinc/java-selenium-framework/security/code-scanning/1

The optimal solution is to add a permissions block at the appropriate level in the workflow YAML file. Since there is only one job defined (test), you can add the permissions block either at the root (applies to all jobs) or directly under the test job. The standard minimal starting point is to set permissions: contents: read, which allows the workflow to read repository contents but not modify them. If future actions require additional permissions, those can be added as necessary with more granular privileges. This change should be made in .github/workflows/ci.yml, immediately after the workflow name: and before on: (for root) or just below the runs-on: line (for job-level permissions).

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. The change implements the principle of least privilege by explicitly defining read-only access to repository contents.

• Added a permissions block with minimal contents: read access to the CI workflow
• Positioned the permissions block at the workflow root level to apply to all jobs

---

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