Python mismatch left hourly reports unwritten

Two hourly jobs stopped before doing any work, which left their reports unwritten.

Their launchd files named the system copy of Python directly, even though our checks used the Homebrew copy. The error log held 78 copies of the same failure before either job began its work.

We pointed both jobs at the Homebrew copy, so every hourly run now uses the Python version we tested.

<caption>Two hourly jobs used a different Python than our checks, so we pointed both at the tested copy.</caption>