feat: daily granularity for sentiment-overview endpoint | LLMO-5307

[aniham]

https://jira.corp.adobe.com/browse/LLMO-5307

Summary

Adds granularity=day query parameter to
GET /org/:spaceCatId/brands/{all|:brandId}/brand-presence/sentiment-overview.

• Backward compatible — omitting granularity or passing week produces the existing
  weeklyTrends response unchanged (now also includes granularity: "week" and
  dailyTrends: [])
• granularity=day returns one bucket per calendar date in dailyTrends; each entry
  carries date (YYYY-MM-DD), week (ISO week string), and the same sentiment/prompt
  shape as weekly
• 90-day range cap enforced for daily granularity; invalid values return 400
• Passes p_granularity to the RPC (requires the mysticat-data-service migration deployed first)
• Adds aggregateSentimentByDay as a JS reference implementation and test oracle
  (same dedup and percentage rules as aggregateSentimentByWeek)

Files changed

File	Change
src/controllers/llmo/llmo-brand-presence.js	aggregateSentimentByDay, updated createSentimentOverviewHandler
test/controllers/llmo/llmo-brand-presence.test.js	9 aggregator tests + 6 handler tests for daily path

Test plan

• npm test passes (11 k+ tests, no regressions)
• Weekly request (no granularity param) → response shape unchanged, weeklyTrends populated
• granularity=day with 28-day range → dailyTrends array, one entry per date
• granularity=day with 91-day range → 400 Date range too large for daily granularity (max 90 days)
• granularity=month → 400 granularity must be 'week' or 'day'

Deploy order

1. mysticat-data-service (RPC migration) — deploy first
2. This PR
3. project-elmo-ui (pass granularity=day for daily-prompt sites) — separate PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!