Standardize orchestrator child-script execution and logging

Every orchestrator invoked its children differently — four near-duplicate
run_job() copies, a differently-shaped run_watchdog(), or plain inline bash
calls, each with its own take on path resolution, pass/fail naming, and
dry-run threading. Extracted one shared run_orch_child() into common.sh so
there's a single place to fix or extend this behavior going forward.

Along the way: watchdog_orchestrator.sh and monthly_maintenance.sh were
checking $VERBOSE, a variable nothing in the codebase ever assigns, so --log
silently did nothing beyond basic logging on those two. Fixed to
$ENABLE_LOGGING. watchdog_orchestrator.sh and array_started.sh had no
trailing exit, so their exit codes reflected whatever the last command
happened to return rather than actual success/failure. transcode_management.sh
had no failure notification and no summary at all. Also made
transcode_management.sh's two-script pipeline config-driven
(TRANSCODE_MANAGEMENT_SCRIPTS in master.conf) instead of hardcoded, for room
to extend it later without editing the orchestrator itself.

Configurations/master.conf

@@ -320,6 +320,16 @@
         "Docker_Essentials/docker_container_stop.sh"    # stop all containers last
     )
 
+# ━━━ Transcode Management ━━━
+# transcode_management.sh runs TRANSCODE_MANAGEMENT_SCRIPTS in order each cron cycle.
+# Schedule: */7 * * * * (every 7 minutes)
+# Order matters — cleanup first so the manager measures real current ramdisk usage,
+# not usage inflated by stale segment files from ended sessions.
+    TRANSCODE_MANAGEMENT_SCRIPTS=(
+        "Transcodes/transcode_cleanup.sh"             # remove aged segment files before usage is measured
+        "Transcodes/transcode_manager.sh"             # flip ramdisk/SSD symlink, write daily log entry
+    )
+
 # ━━━ Watchdog Orchestrator ━━━
 # watchdog_orchestrator.sh runs WATCHDOG_ORCHESTRATOR_SCRIPTS in order each cron cycle.
 # Schedule: */15 * * * * (every 15 minutes)