Review the GITHUB_TOKEN permissions

[serdardalgic]

Right now, any of the GH actions are using the default permissions, which are quite permissive.

GITHUB_TOKEN Permissions
  Actions: write
  Checks: write
  Contents: write
  Deployments: write
  Discussions: write
  Issues: write
  Metadata: read
  Packages: write
  Pages: write
  PullRequests: write
  RepositoryProjects: write
  SecurityEvents: write
  Statuses: write

Any of the GH Action runs shows these permissions during Set up job phase.

Here is the documentation to modify the GITHUB_TOKEN permissions. We may need to experiment on the GH Actions on what kind of permission they may need so that we can remove the unnecessary ones.

Because the 3rd party hooks have already run at least once, and the likelihood of exploitation is low. This Issue is a long term improvement on our CI pipeline, and not a blocker for the releases.

@l0r3bo can you provide more details on how to solve this issue? Thank you in advance.