fix: simplify Playwright configuration for CMS and web apps

- Update Playwright config to use a single 'html' reporter for CMS
- Adjust web app Playwright config to streamline reporter setup
- This change enhances consistency and reduces complexity in test reporting

Author: stephenway

apps/cms/playwright.config.ts

@@ -18,16 +18,7 @@ export default defineConfig({
   /* Opt out of parallel tests on CI. */
   workers: process.env.CI ? 1 : undefined,
   /* Reporter to use. See https://playwright.dev/docs/test-reporters */
-  reporter: [
-    [
-      'html',
-      {
-        outputFolder: process.env.CI
-          ? '../../playwright-report'
-          : 'playwright-report',
-      },
-    ],
-  ],
+  reporter: 'html',
   /* Shared settings for all the projects below. See https://playwright.dev/docs/api/class-testoptions. */
   use: {
     /* Base URL to use in actions like `await page.goto('/')`. */

apps/web/playwright.config.ts

@@ -15,14 +15,7 @@ export default defineConfig({
   workers: process.env.CI ? 1 : undefined,
   /* Reporter to use. See https://playwright.dev/docs/test-reporters */
   reporter: [
-    [
-      'html',
-      {
-        outputFolder: process.env.CI
-          ? '/home/runner/work/overland/overland/playwright-report'
-          : 'playwright-report',
-      },
-    ],
+    ['html'],
     ['json', { outputFile: 'test-results/results.json' }],
     ['junit', { outputFile: 'test-results/results.xml' }],
   ],