GitHub Workflows security hardening

[sashashura]

This PR adds explicit permissions section to workflows. This is a security best practice because by default workflows run with extended set of permissions (except from on: pull_request from external forks). By specifying any permission explicitly all others are set to none. By using the principle of least privilege the damage a compromised workflow can do (because of an injection or compromised third party tool or action) is restricted. It is recommended to have most strict permissions on the top level and grant write permissions on job level case by case.

[sashashura]

Please let me know if you have any questions.

[sashashura]

@narfbg could you please review?

[sashashura]

An example of a workflow run with unrestricted permissions:

[datamweb]

I like this PR, @sashashura why don't you send the same PR for CI4?

[sashashura]

What is CI4?

[datamweb]

What is CI4?

😄 https://github.com/codeigniter4/CodeIgniter4

[gxgpet]

I wonder how this is not the default behavior for GA...

[datamweb]

Maybe because they have given the Repo manager the ability to adjust. However, the setting in file .yml looks better due to its public.