fix(issues): Adding exception capture on Postgres timeout to keep them visible internally

A small addition on top of #87691. There we changed it so these errors are now treated as user errors
but actually these could possibly come from our own Postgres queries taking too long even on reasonable queries, and without capturing
we wouldn't even know they are happening.
Even if thats not the case we want to keep these errors visible in Sentry to be able to monitor them.

Author: yuvmen

src/sentry/api/utils.py

@@ -429,6 +429,10 @@ def handle_query_errors() -> Generator[None]:
         if hasattr(error, "pgcode") and error.pgcode == psycopg2.errorcodes.QUERY_CANCELED:
             if options.get("api.postgres-query-timeout-error-handling.enabled"):
                 sentry_sdk.set_tag("query.error_reason", "Postgres statement timeout")
+                sentry_sdk.capture_exception(
+                    error,
+                    level="warning",
+                )
                 raise Throttled(
                     detail="Query timeout. Please try with a smaller date range or fewer conditions."
                 )