Fix Linux Ozone browser startup

[akshar2324]

Summary

• relaunch Linux once with --ozone-platform=x11 in the browser process arguments
• replace conflicting Wayland or automatic Ozone arguments while preserving unrelated application arguments
• keep app.commandLine aligned for GPU/renderer children and diagnostics
• preserve OPENPETS_ALLOW_WAYLAND=1 as the explicit native-Wayland escape hatch

Root cause

Appending the Ozone switch from main.ts occurs before Electron is ready, but the browser process has already started. On affected Wayland systems this can leave the browser using Wayland while child processes receive X11, causing every OpenPets window to remain invisible.

The replacement process now starts with X11 in its actual argv, so browser, GPU, and renderer processes select the same backend.

Fixes #108.

Validation

• pnpm --filter @open-pets/desktop test:build
• node apps/desktop/.test-dist/tests/linux-ozone-startup.test.js
• existing Wayland backend predicate tests
• pnpm --filter @open-pets/desktop typecheck
• pnpm --filter @open-pets/desktop build
• git diff --check

Ubuntu GUI validation remains pending because the external volume containing the configured VMware VM is not currently mounted. The broad packaging contract also encounters an unrelated existing Windows mouse-forwarding assertion on current main.