fix: wire LOGLEVEL into gunicorn logger level and RQ worker/scheduler

The gunicorn logging config hard-coded level=INFO, ignoring LOGLEVEL.
Patch it at startup via sed. Also pass --logging_level to rq worker
and rqscheduler so their framework logging respects LOGLEVEL.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docker/init_scripts/init

@@ -196,7 +196,8 @@ start_bin_rq_scheduler() {
 		RQ_REDIS_SSL=${REDIS_SSL:-0} \
 		rqscheduler \
 		--path /backend \
-		--pid /tmp/rq_scheduler.pid &
+		--pid /tmp/rq_scheduler.pid \
+		--logging_level "${LOGLEVEL}" &
 }
 
 # Commands to start RQ worker
@@ -219,6 +220,7 @@ start_bin_rq_worker() {
 		--pid /tmp/rq_worker.pid \
 		--url "${redis_url}" \
 		--results-ttl "${TASK_RESULT_TTL:-86400}" \
+		--logging_level "${LOGLEVEL}" \
 		high default low &
 }