fix: move Chromium-specific launch args out of root use block, fix CTA text match

- launchOptions with --disable-dev-shm-usage and --no-sandbox are
  Chromium-specific; passing them to Firefox/WebKit causes errors.
  Move to chromium and android project use blocks only.
- Fix landing page CTA assertion to match actual button text
  ("Get $KRK", "Get Your Edge") instead of generic patterns.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

tests/e2e/07-landing-pages.spec.ts

@@ -21,8 +21,8 @@ test.describe('Landing Pages', () => {
     // Page should contain recognisable KRAIKEN branding
     const body = await page.textContent('body');
     expect(body).toBeTruthy();
-    // Landing page always has a call-to-action button
-    const cta = page.getByRole('link', { name: /app|stake|launch|get started/i }).first();
+    // Landing page always has a call-to-action link ("Get $KRK", "Get Your Edge", etc.)
+    const cta = page.getByRole('link', { name: /get.*krk|get.*edge|stake|launch/i }).first();
     await expect(cta).toBeVisible({ timeout: 15_000 });
 
     await page.screenshot({ path: 'test-results/landing-homepage.png', fullPage: true });