chore(gh): update lock workflow (#2391)

Updates the lock workflow.

Signed-off-by: Ryan Johnson <[email protected]>

Author: tenthirtyam

.github/workflows/lock.yml

@@ -1,21 +1,40 @@
-name: Lock Threads
+---
+name: Lock
 
 on:
   schedule:
-    - cron: '50 1 * * *'
+    - cron: 30 00 * * *
+
+permissions:
+  contents: read
 
 jobs:
   lock:
     runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
     steps:
       - uses: dessant/lock-threads@1bf7ec25051fe7c00bdd17e6a7cf3d7bfb7dc771 # v5.0.1
         with:
-          github-token: ${{ github.token }}
+          github-token: '${{ secrets.GITHUB_TOKEN }}'
           issue-comment: >
-            I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.
-            If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
+            I'm going to lock this issue because it has been closed for 30
+            days. This helps our maintainers find and focus on the active
+            issues.
+
+
+            If you have found a problem that seems similar to this,
+            please open a new issue and complete the issue template so we can
+            capture all the details necessary to investigate further.
           issue-inactive-days: '30'
           pr-comment: >
-            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 issues.
-            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.
+            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
+            issues.
+
+
+            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.
           pr-inactive-days: '30'