feat(analytics): rebrand to analytics engine and establish resource-to-value framework

[victoriacheng15]

Summary

Rebrand the "Collectors" service to "Analytics Engine" and re-architect it into a modular, unit-economics-ready service. This establishes the "Resource-to-Value" framework by integrating Kepler energy data with a new relational schema in TimescaleDB, enabling holistic efficiency and environmental impact tracking.

List of Changes

• Strategic Rebranding: Standardized the service identity and telemetry namespace under "Analytics," eliminating architectural ambiguity and establishing a foundational identity for future FinOps/GreenOps correlation.
• Domain-Isolated Architecture: Re-engineered the service into a modular core, decoupling execution from orchestration to maximize code reuse and lifecycle stability across the monorepo.
• Unit Economics Engine: Transitioned the persistence layer to a high-performance relational schema, enabling the complex relational joins required to correlate infrastructure energy consumption with business value units.
• Resource Attribution: Integrated high-fidelity Kepler energy telemetry to automate the tracking of Carbon Debt and Financial Cost, directly linking physical resource usage to platform outcomes.

Verification

• go test ./internal/analytics/... passed (verified new schema, storage logic, and resource integration).
• Manual scrape of Kepler endpoint confirmed metric availability (active and idle energy counters).
• Verified rebranding consistency across core service infrastructure (Makefile, Docker, K3s manifests).