chore: retrigger isolated CI builds for services with stale bad digests

Restarting these deployments to pick up the corrected B2 secret revealed
they'd been running healthy old pods on top of a bad digest in the
deployment spec all along (silent from an earlier rebuild wave) — the
restart exposed it via ImagePullBackOff/ErrImagePull.

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

apps/catering_services/src/main.rs

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

apps/companies/src/main.rs

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

apps/developers/src/main.rs

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

apps/graphic_designers/src/main.rs

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

apps/makeup_artists/src/main.rs

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

apps/social_media_managers/src/main.rs

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

apps/users/src/main.rs

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

apps/video_editors/src/main.rs

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