Fix commit SHA of github-script action

[AlanGreene]

Changes

Follow-up to #9161
2 uses of the github-script action were referencing an invalid SHA. Update to point to the correct value for the 7.0.1 release.

Not sure why I thought they had already been updated as mentioned in the original PR, I must have been working from a different branch.
/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• pre-commit Passed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[AlanGreene]

/cc @vdemeester

[AlanGreene]

/retest

[vdemeester]

@AlanGreene won't this be fixed by #9195 ?

[AlanGreene]

Ah I didn't see that PR. Yes it updates the SHA to v8, but because 2 of the existing SHAs are wrong it doesn't correctly update the version comment.

If we merge this PR the commits will match the version, then we can rebase the dependabot PR and it should update the comments correctly too.

[vdemeester]

/approve
/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment