Decide between Playwright's launchPersistentContext(userDataDir) and storageState() for reusing authenticated sessions across test runs

Steps

1. Use storageState() to serialize just cookies and localStorage/sessionStorage into a JSON file, then load it into a fresh isolated context with browser.newContext({storageState})
2. Use launchPersistentContext(userDataDir) to reuse a full on-disk browser profile (cookies, cache, IndexedDB, service workers, extensions) when auth or app state depends on more than cookies/web storage
3. Prefer storageState for parallel test workers, since each worker gets its own isolated context from the same snapshot with no profile-directory lock contention
4. Prefer persistent context when the app stores session tokens in IndexedDB or relies on service-worker caches that storageState doesn't capture
5. Give each parallel worker its own userDataDir if using persistent contexts, since Chrome locks the profile directory and won't allow two processes to share one concurrently