Update schedule for lock.yml

To avoid hitting API rate limits.

[skip ci]

Author: diemol

.github/workflows/lock.yml

@@ -4,22 +4,23 @@ name: 'Lock Issues'
 on:
   workflow_dispatch:
   schedule:
-    - cron: '0 0 * * *'
+    - cron: '45 21 * * *'
 
 permissions:
   issues: write
   pull-requests: write
 
 jobs:
   action:
+    if: github.repository_owner == 'seleniumhq'
     runs-on: ubuntu-latest
     steps:
-      - uses: dessant/lock-threads@v2
+      - uses: dessant/lock-threads@v5
         with:
           process-only: 'issues'
-          issue-lock-inactive-days: '30'
+          issue-inactive-days: '30'
           issue-lock-reason: ''
-          issue-lock-comment: >
+          issue-comment: >
             This issue has been automatically locked since there
-            has not been any recent activity after it was closed.
+            has not been any recent activity since it was closed.
             Please open a new issue for related bugs.