fix: use pnpm version from package.json packageManager field

Remove hardcoded pnpm version 8 from workflows and let pnpm/action-setup
automatically detect the version from package.json packageManager field
(pnpm@10.25.0).

This fixes the 'not compatible lockfile' error that was occurring because
the lockfile was generated with pnpm 10 but the workflow was using pnpm 8.

Author: eabdelmoneim

.github/workflows/build.yml

@@ -24,8 +24,7 @@ jobs:
 
       - name: Setup pnpm
         uses: pnpm/action-setup@eae0cfeb286e66ffb5155f1a79b90583a127a68b # v2.4.1
-        with:
-          version: 8
+        # Version is automatically read from package.json packageManager field
 
       - name: Get pnpm store directory
         id: pnpm-cache

.github/workflows/release.yml

@@ -31,8 +31,7 @@ jobs:
 
       - name: Setup pnpm
         uses: pnpm/action-setup@eae0cfeb286e66ffb5155f1a79b90583a127a68b # v2.4.1
-        with:
-          version: 8
+        # Version is automatically read from package.json packageManager field
 
       - name: Install dependencies
         run: pnpm install --frozen-lockfile