The profile-routing file handler keeps a static snapshot of the served
profile homes taken at startup. When 'hermes profile delete' removes a
home underneath a long-lived dashboard process, every record for that
home retries the vanished logs/ path: the managed rotating handler
stats, reopens, fails with FileNotFoundError and routes the error to
stderr — a repeating '--- Logging error ---' loop every logging tick
(#103777).
Fall back to the default home when a routed home's directory no longer
exists, mirroring the cron scheduler's _existing_profile_homes() filter.
The deleted profile's directory is never resurrected on disk and its
records keep flowing to the default home instead of being dropped with
stderr noise.
(cherry picked from commit deab9df17ffd896a61d02f7e25b897d6e2aa46ba)