feat: add agentic traffic endpoints to fetch PG data | LLMO-4000

[calvarezg]

Introduces a new llmo-agentic-traffic controller with 11 site-scoped GET endpoints that query mysticat-data-service via PostgREST, powering the new Postgres-backed Agentic Traffic dashboard.

• New file src/controllers/llmo/llmo-agentic-traffic.js — 9 handler factories wired to existing DB RPCs (rpc_agentic_traffic_kpis, _kpis_trend, _by_region, _by_category, _by_page_type, _by_status, _by_user_agent, _by_url, _movers), plus
  /filter-dimensions (parallel distinct-value queries) and /weeks (min/max date → ISO week list)
• Updated llmo-mysticat-controller.js — adds getSiteAndValidateAccess (site → org → LLMO entitlement check) and instantiates all 11 new handlers
• Updated src/routes/index.js — registers all 11 new routes under GET /sites/:siteId/agentic-traffic/*
• 100% test coverage on all modified files (63 tests); llmo-mysticat-controller.js getSiteAndValidateAccess path fully exercised

New routes:
GET /sites/:siteId/agentic-traffic/kpis
GET /sites/:siteId/agentic-traffic/kpis-trend
GET /sites/:siteId/agentic-traffic/by-region
GET /sites/:siteId/agentic-traffic/by-category
GET /sites/:siteId/agentic-traffic/by-page-type
GET /sites/:siteId/agentic-traffic/by-status
GET /sites/:siteId/agentic-traffic/by-user-agent
GET /sites/:siteId/agentic-traffic/by-url
GET /sites/:siteId/agentic-traffic/filter-dimensions
GET /sites/:siteId/agentic-traffic/weeks
GET /sites/:siteId/agentic-traffic/movers

Please ensure your pull request adheres to the following guidelines:

• make sure to link the related issues in this description. Or if there's no issue created, make sure you
  describe here the problem you're solving.
• when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

If the PR is changing the API specification:

• make sure you add a "Not implemented yet" note the endpoint description, if the implementation is not ready
  yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet.
• make sure you add at least one example of the request and response.

If the PR is changing the API implementation or an entity exposed through the API:

• make sure you update the API specification and the examples to reflect the changes.

If the PR is introducing a new audit type:

• make sure you update the API specification with the type, schema of the audit result and an example

Related Issues

LLMO-4000

[github-actions]

This PR will trigger a minor release when merged.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[solaris007]

🎉 This PR is included in version 1.437.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀