fix: prevent cache collision between integration and E2E tests

The integration tests were failing because they were sharing the same
cache key and path with E2E tests, causing cache collisions. When
integration tests restored a cache created by E2E tests, the data was
in the wrong database schema (E2E uses sharded schemas like shard_1,
while integration uses the default schema).

This fix:
- Gives integration tests a unique cache path (backups/integration.sql)
- Gives each E2E shard a unique cache path (backups/e2e-shard-N.sql)
- Passes the correct DATABASE_URL to cache-db action so seeding/restore
  targets the same schema the tests will use

This ensures each test suite has its own isolated database cache and
prevents the flaky test failures where integration tests found empty
databases (0 results instead of expected data).

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

Author: devin-ai-integration[bot]

.github/workflows/e2e.yml

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

.github/workflows/integration-tests.yml

@@ -79,6 +79,9 @@ jobs:
       - uses: ./.github/actions/dangerous-git-checkout
       - uses: ./.github/actions/yarn-install
       - uses: ./.github/actions/cache-db
+        with:
+          path: backups/integration.sql
+          DATABASE_URL: ${{ secrets.CI_DATABASE_URL }}
       - name: Run Tests
         run: yarn test -- --integrationTestsOnly
       # TODO: Generate test results so we can upload them