Sentry: Add module and version tags #1305

Is your feature request related to a problem?
There's no module or API-version value on Sentry events, so we keep one dashboard per module with hardcoded route lists. log_module only comes from the logger name, so errors from shared code (app.utils.send_callback, app.core.cloud.storage) get no module, and it only lands on logs, not on errors or spans.

Describe the solution you'd like

• Set the module at the start of each request or task: route prefix in core/middleware.py, task name in task_prerun (celery/celery_app.py). Keep the logger map as a fallback.
• Put the same log_module key on errors and spans too, not only logs.
• Add log_api_version (v1 / v2) as its own field; don't fold the version into the module name.
• Goal: one Kaapi · Modules dashboard with Module and Version dropdowns.

Modules

• Knowledge base
• Evals
  • v1
  • v2
• FastEvals
  • v1
  • v2
• LLM-Call
• Config-Version
• Assessment