chore: decouple analytics portainer startup

deploy/portainer/docker-compose.yml

@@ -189,7 +189,6 @@ services:
     restart: unless-stopped
     mem_limit: ${VEHICLE_ANALYTICS_MEM_LIMIT:-1024m}
     depends_on:
-      - gb32960-ingest-app
       - jt808-ingest-app
     environment:
       <<: *common-env

modules/apps/vehicle-history-app/src/test/java/com/lingniu/ingest/historyapp/PortainerComposeResourceLimitsTest.java

@@ -498,6 +498,17 @@ class PortainerComposeResourceLimitsTest {
                 .doesNotContain("VEHICLE_STATE_ENABLED");
     }
 
+    @Test
+    void vehicleAnalyticsComposeDependsOnlyOnJt808Ingest() throws IOException {
+        String compose = Files.readString(repositoryRoot().resolve("deploy/portainer/docker-compose.yml"));
+        String analyticsService = serviceBlock(compose, "vehicle-analytics-app");
+
+        assertThat(analyticsService)
+                .contains("    depends_on:\n      - jt808-ingest-app")
+                .doesNotContain("- gb32960-ingest-app")
+                .doesNotContain("- yutong-mqtt-app");
+    }
+
     @Test
     void vehicleAnalyticsDoesNotInheritRedisStateEnvironment() throws IOException {
         String compose = Files.readString(repositoryRoot().resolve("deploy/portainer/docker-compose.yml"));