fix: adapt Sentry initialization to fix performance tracking not working

[bolinocroustibat]

Fix Sentry performance tracking

Problem

After PR #87, Sentry performance tracking stopped working while error tracking continued to function normally.

Possible Cause

The AioHttpIntegration() instance was being created at module import time in api_tabular/core/sentry.py (when the sentry_kwargs dictionary was defined). This likely happened before sentry_sdk.init() was called in the app modules, which may have prevented the integration from properly hooking into aiohttp's internals for performance tracking.

Error tracking might have been still working because it doesn't require the same level of framework instrumentation - errors can be captured through exception handlers without needing to instrument the request/response cycle.

Solution

Converted sentry_kwargs from a module-level dictionary to a get_sentry_kwargs() function that creates a fresh AioHttpIntegration() instance each time it's called. This ensures the integration is instantiated right when sentry_sdk.init() is called, matching the original behavior before the refactor.

[maudetes]

Ah well spotted, this may explain why it doesn't work properly.
Let's try this, thank you!