Turn history retention into a discrete slider with named presets

[alvst]

The "remove clips older than" day picker offered a handful of choices and no way to say "keep everything". This replaces it with a 10-stop slider of named presets, adding 3 Weeks, 2 Months, and Forever.

What changed

• A new HistoryRetentionPreset drives a 10-stop slider from 1 Day through Forever, replacing the day-choice Picker.
• Forever is stored as historyRetentionDays == 0 — no automatic pruning by age; the existing safety cap still applies.
• The confirm-before-apply dialog for destructive changes is kept exactly as it was: only the presentation of the choice changes, not the safety UX around it.
• Layout fix at the call site: Form(.formStyle(.grouped)) puts every row in a Section's body onto a shared label/control NSGridView, which clamps and right-shifts a bare control regardless of SwiftUI frame modifiers. The slider block moved into the Section's footer, which is plain full-width content.

Screenshots

Before:

After:

Notes for review

• Stored-value migration is safe: every previously stored day count remains a valid stop, so existing installs land on their current setting.
• The confirm dialog still covers every destructive direction — mode switch, tighter preset, and Forever → short.
• No dependencies; merges in any order.

---

This feature should be bundled into v2.

Part of #80.

[momenbasel]

Landed as 3488572 through #104 with a follow-up (d84964d). The slider wrote the draft at every stop it crossed and each write ran the removal check: dragging from 1 Year toward 1 Day committed 6 Months on the way past it, put up the confirm alert for 3 Months while the mouse was still down, and Cancel restored 6 Months instead of 1 Year. It now moves a local value and applies it once editing ends (or on a keyboard step), so Cancel returns to the value the drag started from; the stop under the thumb is still shown live. retentionCutoff returns nil for 0 days instead of treating it as 1, so Forever cannot regress through a new caller. Thanks @alvst.