[TASK] Add configuration support for Content Analytics App (Traditional Implementations only)

[erickgonzalez]

Description

We need to extend the Content Analytics App to support configuring Analytics behavior specifically for Traditional Implementations (non-headless).

This task focuses on enabling UI-level configuration that allows users to control which analytics features are enabled or disabled for Traditional sites, without affecting Headless implementations.

The configuration should allow users to:
• Enable/disable pageviews
• Enable/disable content clicks
• Enable/disable content impressions
• Enable/disable debug mode
• Provide an advanced JSON configuration to fine-tune specific behaviors (e.g. queue settings, impressions behavior, future extensibility)

⚠️ This configuration must explicitly apply only to Traditional Implementations.
It should not be applied to Headless setups.

We need alignment with Product and Design on:
• Wording and labeling in the UI to clearly communicate the scope (Traditional only)
• UX expectations and guardrails to avoid confusion with Headless Analytics

Figma reference (initial exploration):
https://www.figma.com/board/E5Q4OfxboINyYMTf8dBuyr/Analytic-s-App?node-id=0-1&p=f&t=U7wQevx36g3gup6A-0

Acceptance Criteria

• Content Analytics App exposes configuration options
• Users can toggle:
  • Pageviews
  • Content clicks
  • Content impressions
  • Debug mode
• Users can provide an optional advanced JSON configuration for fine-grained control (e.g. queue, impressions)
• Configuration changes are correctly propagated to the analytics runtime
• Clear behavior is defined and documented when configuration changes:
  • Requires restart? (Yes/No)
  • Requires cache flush? If yes, specify which cache(s)
  • Or no action required
• UI copy clearly states that this configuration:
  • Applies to Traditional Implementations only
  • Does not affect Headless Analytics
• Product and Design sign off on wording and UX intent

Priority

High

Additional Context

• This task is intentionally scoped to Traditional Implementations to avoid mixing concerns with Headless Analytics.
• The advanced JSON configuration should be treated as an escape hatch, not required for basic usage.
• Configuration should be forward-compatible with future Analytics features (e.g. queue tuning, new event types).
• Engineering should validate whether config changes:
  • Need application restart
  • Require cache invalidation (and which layer: app, analytics, CDN, etc.)
  • Can be applied dynamically at runtime