fix: remove schema parameter from cache-db DATABASE_URL for E2E

The tj-actions/pg-dump and pg-restore actions pass the DATABASE_URL
directly to libpq, which doesn't support Prisma's ?schema= parameter.
This was causing the cache step to fail with 'invalid connection option
schema' on cache misses.

This fix passes a clean DATABASE_URL (without schema parameter) to the
cache-db action for pg_dump/pg_restore operations. The db-seed step
will still use the job-level DATABASE_URL environment variable which
includes the schema parameter, so Prisma operations work correctly.

Each E2E shard still has a unique cache path to prevent collisions.

Co-Authored-By: Volnei Munhoz <[email protected]>

Author: devin-ai-integration[bot]

.github/workflows/e2e.yml

@@ -96,7 +96,7 @@ jobs:
       - uses: ./.github/actions/cache-db
         with:
           path: backups/e2e-shard-${{ matrix.shard }}.sql
-          DATABASE_URL: ${{ secrets.CI_DATABASE_URL }}?schema=shard_${{ matrix.shard }}
+          DATABASE_URL: ${{ secrets.CI_DATABASE_URL }}
       - uses: ./.github/actions/cache-build
 
       - name: Run Tests