chore: retrigger isolated CI builds for 8 services stuck on bad digests

The last crates/db push (professional.rs role_key fix) rebuilt all 20
services concurrently again, and 8 of them landed ImagePullBackOff on a
digest the registry doesn't have — same congestion pattern as the
employees incident. This commit only touches apps/*/ for the affected
services so CI rebuilds just these 8 in relative isolation.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

apps/catering_services/src/main.rs

@@ -1,3 +1,4 @@
+// retrigger-build-marker
 #![allow(dead_code)]
 
 mod handlers;

apps/companies/src/main.rs

@@ -1,3 +1,4 @@
+// retrigger-build-marker
 #![allow(dead_code)]
 
 mod handlers;

apps/developers/src/main.rs

@@ -1,3 +1,4 @@
+// retrigger-build-marker
 #![allow(dead_code)]
 
 mod handlers;

apps/graphic_designers/src/main.rs

@@ -1,3 +1,4 @@
+// retrigger-build-marker
 #![allow(dead_code)]
 
 mod handlers;

apps/job_seekers/src/main.rs

@@ -1,3 +1,4 @@
+// retrigger-build-marker
 #![allow(dead_code)]
 
 mod handlers;

apps/leads/src/main.rs

@@ -1,3 +1,4 @@
+// retrigger-build-marker
 #![allow(dead_code)]
 
 use axum::{

apps/tutors/src/main.rs

@@ -1,3 +1,4 @@
+// retrigger-build-marker
 #![allow(dead_code)]
 
 mod handlers;

apps/ugc_content_creators/src/main.rs

@@ -1,3 +1,4 @@
+// retrigger-build-marker
 #![allow(dead_code)]
 
 mod handlers;