chore: fix issue/labeler bot

Replace unmaintained actions-ecosystem actions with github-script,
use step outputs instead of env context, and restrict token permissions
to issues: write only.

Author: mikehardy

.github/workflows/issue-labels.yaml

@@ -4,48 +4,61 @@ on:
   issue_comment:
     types: [created]
 
+permissions:
+  issues: write
+
 jobs:
   label-op-response:
     runs-on: ubuntu-latest
     steps:
-      - name: Check if the comment is from the OP
+      - name: Check if the comment is from the issue author
         id: check-op
-        run: |
-          OP=${{ github.event.issue.user.login }}
-          COMMENTER=${{ github.event.comment.user.login }}
-
-          if [ "$OP" = "$COMMENTER" ]; then
-            echo "op_comment=true" >> $GITHUB_ENV
-          else
-            echo "op_comment=false" >> $GITHUB_ENV
-          fi
-
-      - name: Add 'Needs Attention' label if OP responded and it was open
-        if: env.op_comment == 'true' && github.event.issue.state == 'open'
-        # https://github.com/actions-ecosystem/action-add-labels/releases
-        uses: actions-ecosystem/action-add-labels@bd52874380e3909a1ac983768df6976535ece7d8 # v1.1.0
+        uses: actions/github-script@d746ffe35508b1917358783b479e04febd2b8f71 # v9.0.0
         with:
-          labels: 'Needs Attention'
-        env:
-          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
+          script: |
+            const isOpComment =
+              context.payload.comment.user.login ===
+              context.payload.issue.user.login;
+            core.setOutput('op_comment', isOpComment ? 'true' : 'false');
 
-      - name: Remove 'blocked customer-response' label if OP responded and it was open
-        if: env.op_comment == 'true' && github.event.issue.state == 'open'
-        # https://github.com/actions-ecosystem/action-remove-labels/releases
-        uses: actions-ecosystem/action-remove-labels@f5dccab59b9ed79c1a5ddd2ab6d8771449b0250f # v1.3.0
+      - name: Update labels when the issue author responded on an open item
+        if: steps.check-op.outputs.op_comment == 'true' && github.event.issue.state == 'open'
+        uses: actions/github-script@d746ffe35508b1917358783b479e04febd2b8f71 # v9.0.0
         with:
-          labels: 'blocked: customer-response'
-        env:
-          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
+          script: |
+            const issueNumber = context.payload.issue.number;
+            await github.rest.issues.addLabels({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: issueNumber,
+              labels: ['Needs Attention'],
+            });
+            try {
+              await github.rest.issues.removeLabel({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: issueNumber,
+                name: 'blocked: customer-response',
+              });
+            } catch (error) {
+              if (error.status !== 404) {
+                throw error;
+              }
+            }
 
-      - name: Add comment if OP responded but issue was closed
-        if: env.op_comment == 'true' && github.event.issue.state == 'closed'
-        # https://github.com/actions-ecosystem/action-create-comment/releases
-        uses: actions-ecosystem/action-create-comment@5b43c092bf96ebc715dbbe5682ecf3b771223855 # v1.0.0
+      - name: Comment when the issue author responded on a closed item
+        if: steps.check-op.outputs.op_comment == 'true' && github.event.issue.state == 'closed'
+        uses: actions/github-script@d746ffe35508b1917358783b479e04febd2b8f71 # v9.0.0
         with:
-          github_token: ${{ secrets.GH_TOKEN }}
-          body: |
-            In order to prioritize work in this repository, closed issues and pull requests do not regularly receive attention.
-
-            If the underlying issue or pull request still requires attention, opening a new issue with a reproduction
-            after testing with current versions, or reposting the pull request as a new PR may be the most effective way forward.
+          script: |
+            await github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: context.payload.issue.number,
+              body: [
+                'In order to prioritize work in this repository, closed issues and pull requests do not regularly receive attention.',
+                '',
+                'If the underlying issue or pull request still requires attention, opening a new issue with a reproduction',
+                'after testing with current versions, or reposting the pull request as a new PR may be the most effective way forward.',
+              ].join('\n'),
+            });