fix: respect autoAppLaunch config option in test fixture

[farhanlabib]

Problem

autoAppLaunch: false in mobilewright.config was silently ignored by the @mobilewright/test fixture. Even with the option set, the fixture always called terminateApp + launchApp before every test whenever bundleId was configured.

The option was only respected in the launcher path (installAndLaunchApps), not in the test fixture.

Fix

• Added autoAppLaunch as a proper fixture option (reads from config, overridable per-test — consistent with how bundleId works)
• Threaded it into the device fixture
• Guarded the terminate/launch block: the app is only relaunched when autoAppLaunch !== false

Behaviour

Config	Before	After
bundleId set, no autoAppLaunch	relaunches app (default)	relaunches app (default) ✓
bundleId set, autoAppLaunch: true	relaunches app	relaunches app ✓
bundleId set, autoAppLaunch: false	relaunches app ✗	skips relaunch ✓

Use case

Useful for development workflows and test suites where the app is already in the foreground and a cold restart is undesirable (e.g. preserving session state, faster iteration).

// mobilewright.config.ts
export default defineConfig({
  platform: 'android',
  bundleId: 'com.example.app',
  autoAppLaunch: false, // now actually works
});