feat: Allow integrations to define control flow exceptions (#6425)

### Description
Some frameworks we're integrating with use specific exception types for
control flow. If we encounter them, we should not set the status of the
current span to error.

Implement a global ignore list that each integration can populate with
control flow exceptions known to it, so that whenever a span finishes,
it has access to the list and can decide whether the exception that
occurred constitutes an error or not.

#### Issues
- Closes #6408
- Closes https://linear.app/getsentry/issue/PY-2492

#### Reminders
- Please add tests to validate your changes, and lint your code using
`tox -e linters`.
- Add GH Issue ID _&_ Linear ID (if applicable)
- PR title should use [conventional
commit](https://develop.sentry.dev/engineering-practices/commit-messages/#type)
style (`feat:`, `fix:`, `ref:`, `meta:`)
- For external contributors:
[CONTRIBUTING.md](https://github.com/getsentry/sentry-python/blob/master/CONTRIBUTING.md),
[Sentry SDK development docs](https://develop.sentry.dev/sdk/), [Discord
community](https://discord.gg/Ww9hbqr)

Author: sentrivana

sentry_sdk/integrations/aiohttp.py

@@ -42,6 +42,7 @@
     HAS_REAL_CONTEXTVARS,
     SENSITIVE_DATA_SUBSTITUTE,
     AnnotatedValue,
+    _register_control_flow_exception,
     capture_internal_exceptions,
     ensure_integration_enabled,
     event_from_exception,
@@ -111,6 +112,12 @@ def setup_once() -> None:
                 " or aiocontextvars package." + CONTEXTVARS_ERROR_MESSAGE
             )
 
+        # In the aiohttp integration, all of their HTTP responses are Exceptions.
+        # Because they have to be raised and handled by the framework, we need to
+        # register the exceptions as control flow exceptions so that we don't
+        # accidentally overwrite a status of "ok" with "error".
+        _register_control_flow_exception(HTTPException)
+
         ignore_logger("aiohttp.server")
 
         old_handle = Application._handle

sentry_sdk/utils.py

@@ -27,11 +27,6 @@
     # Python 3.10 and below
     BaseExceptionGroup = None  # type: ignore
 
-try:
-    from aiohttp.web_exceptions import HTTPException as AIOHttpHttpException
-except ImportError:
-    AIOHttpHttpException = None
-
 from typing import TYPE_CHECKING
 
 import sentry_sdk
@@ -93,6 +88,10 @@
     "is_sentry_internal_task", default=False
 )
 
+# These exceptions won't set the span status to error if they occur. Use
+# register_control_flow_exception to add to this list
+_control_flow_exception_classes: "list[type]" = []
+
 
 def is_internal_task() -> bool:
     return _is_sentry_internal_task.get()
@@ -1983,15 +1982,16 @@ def get_current_thread_meta(
     return None, None
 
 
+def _register_control_flow_exception(exc_type: type) -> None:
+    _control_flow_exception_classes.append(exc_type)
+
+
 def should_be_treated_as_error(ty: "Any", value: "Any") -> bool:
     if ty == SystemExit and hasattr(value, "code") and value.code in (0, None):
         # https://docs.python.org/3/library/exceptions.html#SystemExit
         return False
 
-    # In the aiohttp integration, all of their HTTP responses are Exceptions.
-    # Because they have to be raised and handled by the framework, we need this check so
-    # that we don't accidentally overwrite a status of "ok" with "error" here.
-    if AIOHttpHttpException and isinstance(value, AIOHttpHttpException):
+    if issubclass(ty, tuple(_control_flow_exception_classes)):
         return False
 
     return True