🌱 Add token permissions to verify.yml workflow

[varunsh-coder]

• Please check if the PR fulfills these requirements

• Tests for the changes have been added (for bug fixes / features)
• PR title follows the guidelines defined in https://github.com/ossf/scorecard/blob/main/CONTRIBUTING.md#pr-process

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  Adds minimum token permissions to the verify.yml workflow

• What is the current behavior? (You can also link to an open issue here)
  verify.yml workflow does not have token permissions set

• What is the new behavior (if this is a feature change)?
  verify.yml workflow has token permissions. Permissions were added automatically using https://app.stepsecurity.io/secureworkflow

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  No

• Other information:
  Step Security website now adds permissions:read-all at top level as discussed in Token-Permissions check clarification #1128. The automation adds a new line above jobs:. Let me know if there should be no new line or there should also be new line above the permissions: read-all

[laurentsimon]

@naveensrinivasan this PR seems ok to me because the action does not checkout the code or run it: it only looks at the PR description. Are we going to split this workflow using pull_request and run_workflow
in the future? I don't think we gain anything by doing that though, since a takeover of the action would also allow the malicious PR to return success.

[laurentsimon]

Thanks!

[github-actions]

Integration tests success for
[645f617]
(https://github.com/ossf/scorecard/actions/runs/1491601893)

[github-actions]

Integration tests success for
[f022e48]
(https://github.com/ossf/scorecard/actions/runs/1500162024)

[github-actions]

Integration tests success for
[fc6b5c2]
(https://github.com/ossf/scorecard/actions/runs/1532692297)