fix(settings): compare restart notices against the running app, fix CI fallout

The restart notice now lists only the restart controls whose saved value
differs from what the running app uses: the stored values at first load,
or what the embedded engine reports it actually runs for the frame-copy
opt-in. Saving the launch value back withdraws the notice instead of
leaving it up with no chip to explain it. The refresh reads the current
list untracked and writes only a changed one, because the engine probe
effect calls it.

CI: the zoneless checklist dropped the deleted Reset section component, and
the theme-tokens Electron E2E floats the recording folder label on the
Playback page now that the settings selects carry no floating label.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/architecture/zoneless-migration.md

@@ -85,7 +85,6 @@ picker), so each marks itself on the form's `events` through
 - [x] `apps/web/src/app/settings/settings-general-section.component.ts`
 - [x] `apps/web/src/app/settings/settings-playback-section.component.ts`
 - [x] `apps/web/src/app/settings/settings-remote-control-section.component.ts`
-- [x] `apps/web/src/app/settings/settings-reset-section.component.ts`
 - [x] `apps/web/src/app/settings/settings-tmdb-section.component.ts`
 - [x] `apps/web/src/app/settings/settings-unsaved-changes-dialog.component.ts`