fix(ci): unblock gh-pages deploy under yarn

The deploy workflow uses yarn v1, which ignores npm's overrides field.
Add a matching resolutions entry so yarn also pins webpack to ~5.100.0
and sidesteps the ProgressPlugin schema regression introduced in 5.101.

While here, bump the deploy workflow actions (checkout/setup-node to v4)
and pin Node to 20 — 'lts/*' on setup-node v3 was resolving to a
too-new version in CI.

Author: Aldiwildan77

.github/workflows/gh-pages.yml

@@ -12,12 +12,12 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4
 
       - name: Setup Node
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
-          node-version: 'lts/*'
+          node-version: '20'
 
       - name: Build
         run: |

package.json

@@ -47,5 +47,8 @@
   },
   "overrides": {
     "webpack": "~5.100.0"
+  },
+  "resolutions": {
+    "webpack": "~5.100.0"
   }
 }