super-linter logs are noisy due to github 403 errors

Describe the bug
Super linter outputs these errors which make it hard to see the real linting errors maybe a github token is needed or the github status feature could be turned off

Suggested fix from https://github.com/super-linter/super-linter/issues/5223 see also https://github.com/super-linter/super-linter?tab=readme-ov-file#get-started

permissions:
  actions: read
  checks: read
  # To report GitHub Actions status checks
  statuses: write

See
https://github.com/super-linter/super-linter/issues/5223

2026-07-24 12:24:17 [ERROR] Failed to call GitHub API (https://api.github.com/repos/microsoft/AzureTRE/statuses/30d4517899ded3f69c03acc8ac531799b6b7b1b7) with POST HTTP method: curl: (22) The requested URL returned error: 403

Steps to reproduce

1. Create a PR and review linting output

Azure TRE release version (e.g. v0.14.0 or main):
main

Deployed Azure TRE components - click the (i) in the UI:
N/A

Start with the GitHub Actions workflow that runs super-linter and review its permissions against the suggested actions, checks, and statuses settings. Reproduce the 403 during a pull request, then verify that super-linter no longer emits the noisy GitHub API error while genuine linting errors remain visible.