fix: run hydrated queue after daemon restart

[MarcStdt]

Summary\n- trigger the runtime queue after hydration restores persisted procedure state\n- cover the production startup ordering where RuntimeSupervisor starts the session before Hydrate populates the queue\n\n## Why\nAfter daemon restart, a restart-mode command with a running Kubernetes job could remain in procedure state as running without reattaching the queue worker. If the rehydrated coldstarter job later completed, no waiter advanced the procedure to done or started the next procedure.\n\n## Tests\n- go test ./apps/druid/core/services -run 'TestRuntimeSupervisorStartRunsHydratedRestartCommand|TestRuntimeSupervisorStartHydratesRunningScroll|TestRuntimeSessionHydratePreservesProcedureStateWhenReattachingRunningRestart'\n- go test ./apps/druid/core/services ./internal/runtime/kubernetes ./internal/runtime/docker ./internal/core/services\n- go test ./...\n- git diff --check

[druid-infra]

Error: This repo is not allowlisted for Atlantis.