Fix logger name misattributed to sentry_sdk.integrations.logging

[pgetta]

Problem

Since the Sentry integration (#667), every log emitted by third-party libraries through stdlib logging is reported with "name":"sentry_sdk.integrations.logging" instead of the originating module:

{"time":"...","level":"INFO","name":"sentry_sdk.integrations.logging","message":"HTTP Request: GET https://.../userinfo \"HTTP/1.1 200 OK\"",...}

Cause

Sentry's default LoggingIntegration monkeypatches logging.Logger.callHandlers, inserting a sentry_sdk frame into the call stack between the stdlib logging frames. InterceptHandler.emit locates the original caller by walking frames and skipping only frames from the logging module, so the walk now stops at Sentry's wrapper. Loguru then derives record["name"] (and function/line) from that frame instead of the real caller. Known issue with the loguru intercept recipe: Delgan/loguru#509.

Fix

Extend the frame walk to also skip frames whose module is sentry_sdk.*. Checked via the frame's __name__ so app/logger.py doesn't need to import sentry_sdk, preserving the init ordering documented in app/sentry.py.

Testing

• New regression test in tests/test_logger.py: initializes sentry (asserting Logger.callHandlers is actually patched), routes a stdlib log through InterceptHandler, and asserts the loguru record is attributed to the calling module/function. Fails with 'sentry_sdk.integrations.logging' == 'tests.test_logger' without the fix.
• Full suite passes (1068 tests).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
pytest	97.84% <100.00%> (+0.06%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
app/logger.py	90.00% <100.00%> (+14.00%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[pgetta]

Closing in favour of #678