Depend on the fixed crypto stack, and let Lock Threads run again

@pezkuwi/util, util-crypto and x-fetch now require ^14.0.26, which brings
@pezkuwi/wasm-crypto 7.5.20 in place of 7.5.17. The lockfile moves with it.

axios moves to ^1.20.0 in resolutions, with the lockfile entries that the
Dependabot PR for it (#11) left out; without them `yarn install --immutable`
refused to run and every check on that PR failed.

Lock Threads has failed on every scheduled run: lock-threads v4 rejects a
github-token longer than 100 characters, and GitHub's tokens now are. v6.0.2
fixes the validation. Since v5 the action also locks discussions by default;
process-only keeps it to issues and pull requests, as before and as the job's
permissions allow.

.github/workflows/lock.yml

@@ -16,9 +16,10 @@ jobs:
     env:
       YARN_ENABLE_SCRIPTS: false
     steps:
-      - uses: dessant/lock-threads@c1b35aecc5cdb1a34539d14196df55838bb2f836 # v4.0.0
+      - uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2
         with:
           github-token: ${{ github.token }}
+          process-only: 'issues, prs'
           issue-inactive-days: '7'
           issue-comment: >
             This thread has been automatically locked since there has not been