Fix Corepack/Yarn caching issue in CI workflows

- Remove cache: yarn from setup-node action to prevent yarn usage before corepack enable
- Enable corepack immediately after Node.js setup
- Add manual yarn caching using actions/cache@v4 with proper cache directory path
- This resolves the packageManager field conflict in CI

.github/workflows/build.yml

@@ -18,11 +18,22 @@ jobs:
         uses: actions/setup-node@v6
         with:
           node-version: "22"
-          cache: "yarn"
 
       - name: Enable Corepack
         run: corepack enable
 
+      - name: Get yarn cache directory path
+        id: yarn-cache-dir-path
+        run: echo "dir=$(yarn config get cacheFolder)" >> $GITHUB_OUTPUT
+
+      - name: Cache yarn dependencies
+        uses: actions/cache@v4
+        with:
+          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
+          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
+          restore-keys: |
+            ${{ runner.os }}-yarn-
+
       - name: Install dependencies
         run: yarn install --frozen-lockfile
 

.github/workflows/lint.yml

@@ -18,11 +18,22 @@ jobs:
         uses: actions/setup-node@v6
         with:
           node-version: "22"
-          cache: "yarn"
 
       - name: Enable Corepack
         run: corepack enable
 
+      - name: Get yarn cache directory path
+        id: yarn-cache-dir-path
+        run: echo "dir=$(yarn config get cacheFolder)" >> $GITHUB_OUTPUT
+
+      - name: Cache yarn dependencies
+        uses: actions/cache@v4
+        with:
+          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
+          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
+          restore-keys: |
+            ${{ runner.os }}-yarn-
+
       - name: Install dependencies
         run: yarn install --frozen-lockfile