feat: make route control and replay configurable per environment/app

Added routeControlEnabled and replayEnabled to ResolvedContainerConfig,
flowing through the three-layer config merge (global -> env -> app).
Both default to true. Admins can disable them per environment (e.g.
prod) via the defaultContainerConfig JSONB, or per app via the app's
containerConfig JSONB.

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

cameleer3-server-core/src/main/java/com/cameleer3/server/core/runtime/ConfigMerger.java

@@ -28,7 +28,9 @@ public final class ConfigMerger {
                 stringVal(appConfig, envConfig, "routingDomain", global.routingDomain()),
                 stringVal(appConfig, envConfig, "serverUrl", global.serverUrl()),
                 intVal(appConfig, envConfig, "replicas", 1),
-                stringVal(appConfig, envConfig, "deploymentStrategy", "blue-green")
+                stringVal(appConfig, envConfig, "deploymentStrategy", "blue-green"),
+                boolVal(appConfig, envConfig, "routeControlEnabled", true),
+                boolVal(appConfig, envConfig, "replayEnabled", true)
         );
     }
 

cameleer3-server-core/src/main/java/com/cameleer3/server/core/runtime/ResolvedContainerConfig.java

@@ -17,7 +17,9 @@ public record ResolvedContainerConfig(
         String routingDomain,
         String serverUrl,
         int replicas,
-        String deploymentStrategy
+        String deploymentStrategy,
+        boolean routeControlEnabled,
+        boolean replayEnabled
 ) {
     public long memoryLimitBytes() {
         return (long) memoryLimitMb * 1024 * 1024;