revert(ci): drop turbopackFileSystemCacheForBuild and restore actions/cache (#4500)

Build times grew monotonically from ~200s to 1305s (~6x) after #4478 landed.
The Turbopack FS cache flag combined with sticky-disk persistence caused
unbounded cache growth. Reverting both — keeping the poweredByHeader and
optimizePackageImports trim from the original PR.

Author: waleedlatif1

.github/workflows/test-build.yml

@@ -44,11 +44,13 @@ jobs:
           key: ${{ github.repository }}-turbo-cache
           path: ./.turbo
 
-      - name: Mount Next.js build cache (Sticky Disk)
-        uses: useblacksmith/stickydisk@v1
+      - name: Restore Next.js build cache
+        uses: actions/cache@v5
         with:
-          key: ${{ github.repository }}-nextjs-cache
           path: ./apps/sim/.next/cache
+          key: ${{ runner.os }}-nextjs-${{ hashFiles('bun.lock') }}
+          restore-keys: |
+            ${{ runner.os }}-nextjs-
 
       - name: Install dependencies
         run: bun install --frozen-lockfile

apps/sim/next.config.ts

@@ -98,7 +98,6 @@ const nextConfig: NextConfig = {
   experimental: {
     optimizeCss: true,
     preloadEntriesOnStart: false,
-    turbopackFileSystemCacheForBuild: true,
     optimizePackageImports: [
       'lodash',
       'framer-motion',