[ITEP-83027] Controller with Analytics only mode

[dmytroye]

📝 Description

This PR introduces an analytics-only mode for the Controller service, allowing it to consume tracked objects from a separate Tracker service via MQTT rather than performing tracking internally.

Changes:

• Added --analytics-only command-line flag and CONTROLLER_ENABLE_ANALYTICS_ONLY environment variable (defaults to false)
• Modified Controller to skip tracker initialization when analytics-only mode is enabled
• Implemented tracked object caching and deserialization from MQTT messages
• Optimized early-exit checks in camera/scene data processing for better performance
• Added Docker Compose and Kubernetes/Helm deployment support

✨ Type of Change

Select the type of change your PR introduces:

• 🐞 Bug fix – Non-breaking change which fixes an issue
• 🚀 New feature – Non-breaking change which adds functionality
• 🔨 Refactor – Non-breaking change which refactors the code base
• 💥 Breaking change – Changes that break existing functionality
• 📚 Documentation update
• 🔒 Security update
• 🧪 Tests
• 🚂 CI

🧪 Testing Scenarios

Describe how the changes were tested and how reviewers can test them too:

• ✅ Tested manually
• 🤖 Ran automated end-to-end tests

✅ Checklist

Before submitting the PR, ensure the following:

• 🔍 PR title is clear and descriptive
• 📝 For internal contributors: If applicable, include the JIRA ticket number (e.g., ITEP-123456) in the PR title. Do not include full URLs
• 💬 I have commented my code, especially in hard-to-understand areas
• 📄 I have made corresponding changes to the documentation
• ✅ I have added tests that prove my fix is effective or my feature works

[dmytroye]

Discussed with @dmytroye , External tracker service that subscribes to DATA_CAMERA and publishes tracks in a scene on DATA_SCENE should also subscribe to DATA_EXTERNAL. However if this is not in the current scope of external tracker service , then I suggest completely disabling scene hierarchy in controller's analytics only mode.

Points to consider:

• Controller in analytics only mode can not fuse tracks from child with tracks in the scene. However it can republish events that are rightly transformed. But they don't hold any significance without tracks.
• In the else part of subscriptions in local child scene and remote child scene, subscribing to DATA_SCENE will yield in republishing the same tracks got from the child scene under the same topic. Redundant.

@sarthakdeva-intel Scene hierarchy in controller's analytics only mode disabled for objects and events republish.

[sarthakdeva-intel]

Have you confirmed support of

1. environmental and attribute sensors
2. attribute persistence (which is unlikely as the tracker sits outside having no knowledge about what attributes to persist)?

If not let's add that here as well: Sensors in Scene not supported and attribute persistence across moving objects not supported.

[dmytroye]

Added - aa4ec21. Sensor data still accessible on event topic.