fix: use pnpm filter commands in Playwright webServer for CI compatibility

- Update webServer commands to use pnpm --filter instead of relative cd commands
- Ensures commands work from any directory context (repo root in CI vs local directory)
- Maintains environment-aware LEGACY_MODE support for webpack/rspack switching
- All 13/13 tests still passing locally with updated configuration

This resolves the CI directory context issue where Playwright webServer
commands were failing due to relative path assumptions.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: ScriptedAlchemy

advanced-api/dynamic-remotes/playwright.config.ts

@@ -31,19 +31,19 @@ export default defineConfig({
 
   webServer: [
     {
-      command: `cd app1 && pnpm ${process.env.LEGACY_MODE ? 'legacy:start' : 'start'}`,
+      command: `pnpm --filter dynamic-remotes_app1 ${process.env.LEGACY_MODE ? 'legacy:start' : 'start'}`,
       port: 3001,
       timeout: 120000,
       reuseExistingServer: !process.env.CI,
     },
     {
-      command: `cd app2 && pnpm ${process.env.LEGACY_MODE ? 'legacy:start' : 'start'}`,
+      command: `pnpm --filter dynamic-remotes_app2 ${process.env.LEGACY_MODE ? 'legacy:start' : 'start'}`,
       port: 3002,
       timeout: 120000,
       reuseExistingServer: !process.env.CI,
     },
     {
-      command: `cd app3 && pnpm ${process.env.LEGACY_MODE ? 'legacy:start' : 'start'}`,
+      command: `pnpm --filter dynamic-remotes_app3 ${process.env.LEGACY_MODE ? 'legacy:start' : 'start'}`,
       port: 3003,
       timeout: 120000,
       reuseExistingServer: !process.env.CI,