fix(e2e): forward mock option from setRecipeFixture to configureDevServer

setRecipeFixture accepted a `mock` option in its call sites but silently
discarded it — RecipeFixtureOptions had no `mock` property and the
destructuring never extracted it. Since the e2e directory lacks a
tsconfig, TypeScript couldn't catch the extra property.

Without `mock` reaching configureDevServer:
- createMockEnvFile was never called (no scenario env var)
- The MSW entry point was never set (no fetch interception)
- No session cookie injection occurred
- account.tsx's isLoggedIn check always returned false
- All authenticated tests redirected to /account/login

The fix adds `mock` to RecipeFixtureOptions and forwards it through to
configureDevServer, which already handles it correctly.

Author: itsjustriley

e2e/fixtures/recipe.ts

@@ -1,4 +1,5 @@
 import {test, configureDevServer} from './index';
+import type {MswScenario} from './msw/scenarios';
 import path from 'node:path';
 import {
   stat,
@@ -48,6 +49,14 @@ export type RecipeFixtureOptions = {
    * These override any defaults but don't override the test store env file.
    */
   envOverrides?: Record<string, string>;
+  /**
+   * MSW mock scenario to enable session injection and API interception.
+   * When set, the dev server starts with the MSW entry point and writes
+   * the scenario name to the env file for runtime use.
+   */
+  mock?: {
+    scenario: MswScenario;
+  };
 };
 
 export const setRecipeFixture = (options: RecipeFixtureOptions) => {
@@ -56,6 +65,7 @@ export const setRecipeFixture = (options: RecipeFixtureOptions) => {
     storeKey = 'hydrogenPreviewStorefront',
     useCache = true,
     envOverrides = {},
+    mock,
   } = options;
 
   const isLocal = !storeKey.startsWith('https://');
@@ -87,6 +97,7 @@ export const setRecipeFixture = (options: RecipeFixtureOptions) => {
   configureDevServer({
     storeKey,
     projectPath: isLocal ? recipeFixturePath : undefined,
+    mock,
   });
 };