fix(play-setup): persist per-game resolution + add independent Frame Rate row

[FabianZettl]

Context

On the Play Setup screen, Where It Runs and Tuning already persist their per-game choice across sessions (NovaLaunchModeOverrides, AutoQualityProfilePreferences). Resolution did not: picking a resolution worked for the launch it was chosen for, but after a disconnect/reconnect (or any time NovaGameDetailActivity gets recreated) the row silently reset back to the planner's recommendation, as if the choice had never been made.

Root cause

chosenResolution (NovaGameDetailActivity.kt) was a plain mutableStateOf<NovaDisplayResolutionChoice?>(null) Activity-scoped Compose state field with no backing store at all - it only ever got read once by launchOptimization() to build the one-shot launch override blob, then died with the Activity on finish(). There was no persistence path to hook into; the row just looked like a setting without being one.

What this does

Adds NovaResolutionOverrides, mirroring the existing NovaLaunchModeOverrides pattern: only the chosen NovaDisplayResolutionChoice.id is persisted (SharedPreferences, keyed per game), since the NovaDisplayResolutionChoice objects themselves are rebuilt fresh from the planner on every screen open anyway.

• chooseResolution() now saves the id alongside updating the in-memory state.
• chosenResolution's initial value is resolved from the saved id against that open's resolutionPlanner(game).visibleChoices via a new loadResolutionOverride() helper.

No changes to the picker UI, the planner, or the launch-time override blob - this only fixes what happens to the choice between launches.

Testing

• ./gradlew :app:compileRootDebugKotlin - builds clean
• Built and installed on a real device (AYN Thor, debug build). In Play Setup for Crisis Core –FINAL FANTASY VII– REUNION, changed Resolution to Performance (960x540), then force-stopped the app entirely (not just backgrounded/disconnected) and relaunched. Reopened Play Setup for the same game: Resolution still showed 960x540 with the "Chosen here · applies at launch" caption. This is a stronger test than a session disconnect since it confirms the fix survives full process death, not just Activity recreation within a live process.

[FabianZettl]

Added a second, related change on top of the resolution-persistence fix: an independent Frame Rate row in Play Setup, between Resolution and Tuning.

Why

Resolution and frame rate were coupled - each resolution choice from the planner carries its own paired rate (e.g. 1440x810x60), and the only way to pin an fps independently of that was the global Tuning = High FPS profile plus the app-wide Settings frame rate. There was no per-game way to say "this resolution, but 90fps."

The engine to compose an independent fps into the launch blob already existed (NovaLaunchStreamOverride.compose's fpsOverride parameter, previously fed only by highFpsPin()) - this adds a second entry point into it from Play Setup itself.

What this does

• New Frame Rate row: Auto (falls back to whatever the resolution choice or host plan would have used) plus 30/60/90/120 FPS.
• An explicit pick wins over the implicit Tuning = High FPS pin, since a pin made by name here is a more specific answer than one inferred from a quality profile.
• Persists per-game via NovaFrameRateOverrides, mirroring the resolution-override fix earlier in this same branch - same store shape, same lifecycle.

Testing

• ./gradlew :app:compileRootDebugKotlin - builds clean
• Built and installed on a real device (AYN Thor, debug build). For Crisis Core –FINAL FANTASY VII– REUNION: set Frame Rate to 90 FPS independently of Resolution (left at 1920x1080), force-stopped Nova entirely, relaunched, reopened Play Setup - Frame Rate still read 90 FPS with "Chosen here · applies at launch". Set it back to Auto and confirmed it correctly fell back to deriving the rate from the resolution choice again (60 FPS, matching 1920x1080's own paired rate) rather than getting stuck on the last pin.