Story: Entity classification and drift baseline: ores.analytics

Bring ores.analytics to the same proven state as the ores.refdata pilot: every codegen-eligible entity bound to a profile or recorded as a genuine no-match, zero-diff regeneration verified, and any real gap the check surfaces fixed rather than skipped. Once trusted, analytics-cpp is added to the CI regeneration-drift check.

• Every ores.analytics entity is bound to a matching Variability Profile, or recorded as a genuine no-match with a documented reason.
• Every rebound entity is regenerated and diffed against its pre-rebind checked-in output; zero diff is the pass condition, and any non-zero diff is fixed, not worked around.
• Full local build clean, validate_schemas.sh green, full ctest suite green after regeneration.
• check_component_drift.py –components is extended to include analytics-cpp, and the refdata-codegen-drift CI job is updated so future PRs touching ores.analytics fail on any regeneration drift.
• The superseded ad hoc task 'Apply safe drift to analytics-cpp' is marked ABANDONED, pointing here.
• The known starting-point wrinkles already recorded (service_find_by_uuid on pricing_model_config/pricing_model_product/pricing_model_product_parameter, service_find_by_code on pricing_model_config, service_find_prefix on pricing_engine_type) are resolved as part of reaching zero drift.