[Feature] Service Management (start/stop/enable services)

Problem Statement

TaskSmack has no way to view or control system services. Windows Task Manager's Services tab and TaskSlinger's service management are both standard in this category. tasksmack.md's own "Current Engineering Direction" section already names "service/startup management" as a candidate area.

Proposed Solution

A new panel/tab listing services (name, status, startup type) with start/stop/restart/enable/disable actions.

Alternatives Considered

Ship a read-only view first (list + status, no control actions) before adding control, since service control actions typically need elevation and carry real risk (stopping the wrong service can affect system stability) — a reasonable phased scope.

Additional Context

n/a

Implementation Notes

• Linux: systemd D-Bus API (org.freedesktop.systemd1) preferred over shelling out to systemctl; fallback to parsing systemctl list-units --type=service output if D-Bus access isn't available.
• Windows: Service Control Manager (OpenSCManager/EnumServicesStatusEx for listing, ControlService/ChangeServiceConfig for actions).
• New Platform interface pair (e.g. IServiceProbe/IServiceActions) alongside the existing IProcessActions pattern; wired from the App composition root the same way ProcessesPanel wires IProcessActions today.
• Control actions should reuse the existing confirmation-dialog pattern (ProcessDetailsPanel::renderConfirmDialog) given the risk of stopping the wrong service.

Start by reading tasksmack.md's Current Engineering Direction, then trace the existing IProcessActions pattern, ProcessesPanel wiring, and ProcessDetailsPanel::renderConfirmDialog. Determine whether the first milestone is read-only service listing or full control actions across Linux and Windows. Done means the agreed service panel and its scoped operations work through the App composition root with confirmation for risky actions.