restic: drop scheduled forget across all 6 hosts

Forget against an --append-only rest-server fails every night (delete
ops blocked). The resulting daily failure cluttered service status and
logs without ever actually retiring old snapshots. Schedule is now
removed from the forget block in all six profiles; the keep-daily /
keep-weekly / keep-monthly / keep-yearly policy remains so manual
invocations (during prune ceremonies, when --append-only is
temporarily off) honor the intended retention.

Files:
  configs/restic/ana-docker/profiles.yaml
  configs/restic/ana-ml2/profiles.yaml
  configs/restic/nh3-docker/profiles.yaml
  configs/restic/esh-docker-vm/profiles.yaml
  configs/restic/vm-esh-nas/profiles.yaml
  configs/restic/nh3-dev/profiles.yaml

Each file has an inline comment marking why the schedule was dropped
so a future reader doesn't re-add it thinking it was an oversight.

STATUS.md: removed the "install Backrest nightly-restart timer" line
item. User confirmed the UI timeout hits even at startup, so periodic
restart wouldn't actually help. Root cause remains deferred.

STATUS.md

@@ -64,10 +64,12 @@ significant work lands — don't let it drift quietly.
    comment out `schedule:` under the `forget` block in profiles.yaml;
    redeploy; run `resticprofile unschedule forget` on each host. ~15 min.
 
-4. **Install the Backrest nightly-restart systemd timer** on ana-docker as
-   a safety net for the intermittent UI timeout. Cheap insurance
-   regardless of root cause. ~2 min. Commands in session transcript
-   (search for `backrest-nightly-restart.timer`).
+<!-- 2026-04-21: Dropped the "nightly-restart safety net" idea — user
+     confirmed Backrest UI chokes even right after startup, so periodic
+     restart wouldn't reliably help. Root cause still unknown; see
+     item under "Research / deferred" below. -->
+
+4. _(removed — see note above)_
 
 ### 🟧 Real work (dedicated session each)