ci: add minimum GitHub token permissions for workflows

[ashishkurmi]

Description

This PR adds minimum token permissions for the GITHUB_TOKEN in GitHub Actions workflows using secure-workflows.

The GitHub Actions workflow has a GITHUB_TOKEN with write access to multiple scopes. Here is an example of the permissions in one of the workflow runs:
https://github.com/hashicorp/terraform/actions/runs/3167052373/jobs/5157241888#step:1:19

After this change, the scopes will be reduced to the minimum needed for the following workflows:

• issue-comment-created.yml
• lock.yml
• main.yml

Motivation and Context

• This is a security best practice, so if the GITHUB_TOKEN is compromised due to a vulnerability or compromised Action, the damage will be reduced.
• GitHub recommends defining minimum GITHUB_TOKEN permissions.
• The Open Source Security Foundation (OpenSSF) Scorecards also treats not setting token permissions as a high-risk issue. This change will help increase the Scorecard score for this repository.

Signed-off-by: Ashish Kurmi akurmi@stepsecurity.io

[crw]

Thanks for this submission! The safety and security of our products is deeply important to us. Our build process is designed and vetted by our internal release engineering and security teams. Although we do not typically accept pull requests for the build and release process, I will run this PR past those teams for review. Thanks for your consideration on this issue.

[crw]

Hi @boahc077, this PR looked familiar so I did a little digging, and this appears to be almost identical to #31863 -- I am going to close this PR, can you please leave any feedback on implementation in the previously-opened PR? Thanks!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.