feat(python): Replace experimental logs options with regular ones (#14513)

We'll be promoting the `enable_logs` and `before_send_log` options to
regular SDK options. (We'll still keep the experimental counterparts
until 3.0.)


---------

Co-authored-by: Alex Krawiec <[email protected]>

Author: sentrivana

docs/platforms/python/configuration/options.mdx

@@ -176,7 +176,7 @@ Please note that the Sentry server [limits HTTP request body size](https://devel
 
 The number of characters after which the values containing text in the event payload will be truncated.
 
-In SDK versions prior to 2.34.0, the default was 1024.
+In SDK versions prior to `2.34.0`, the default was `1024`.
 
 </SdkOption>
 
@@ -245,8 +245,19 @@ The callback typically gets a second argument (called a "hint") which contains t
 
 </SdkOption>
 
+<SdkOption name="before_send_log" type='Optional[Callable[Log, Hint] -> Optional[Log]]' defaultValue='None'>
+
+A function that will be called for each log. It can be used to modify the log
+before it's sent to Sentry or to filter specific logs out altogether (if it returns
+`None`).
+
+New in SDK version `2.35.0`. Prior to `2.35.0`, this option was experimental.
+
+</SdkOption>
+
 <PlatformContent includePath="/performance/traces-sampler-config-option" />
 
+
 ## Transport Options
 
 Transports are used to send events to Sentry. Transports can be customized to some degree to better support highly specific deployments.
@@ -412,3 +423,15 @@ In `trace` mode, the profiler starts and stops automatically based on active spa
 A number between `0` and `1`, controlling the percentage chance a given session will be profiled. The sampling decision is evaluated only once at SDK initialization.
 
 </SdkOption>
+
+
+## Logs Options
+
+<SdkOption name="enable_logs" type='bool' defaultValue='False'>
+
+Enables Sentry structured logs, allowing you to use the `sentry_sdk.logger` APIs
+to send logs to Sentry. This option must be set to `True` to automatically capture logs from Python’s built-in logging module or other supported logging integrations.
+
+New in SDK version `2.35.0`. Prior to `2.35.0`, this option was experimental.
+
+</SdkOption>

docs/platforms/python/integrations/logging/index.mdx

@@ -54,7 +54,7 @@ main()
 - `"An exception happened"` will send the current exception from `sys.exc_info()` with the stack trace and everything to the Sentry Python SDK. If there's no exception, the current stack will be attached.
 - The debug message `"I am ignored"` will not surface anywhere. To capture it, you need to lower `level` to `DEBUG` (See below).
 
-Log records can additionally also be captured as [Sentry logs](/platforms/python/logs/) as long as the `enable_logs` experimental option is `True`.
+Log records can additionally also be captured as [Sentry logs](/platforms/python/logs/) as long as the `enable_logs` option is `True`.
 
 ```python
 import logging
@@ -129,7 +129,7 @@ You can pass the following keyword arguments to `LoggingIntegration()`:
 
 - `event_level` (default `ERROR`): The Sentry Python SDK will report log records with a level higher than or equal to `event_level` as events as long as the logger itself is set to output records of those log levels (see note below). If a value of `None` occurs, the SDK won't send log records as events.
 
-- `sentry_logs_level` (default `INFO`): The Sentry Python SDK will capture records with a level higher than or equal to `sentry_logs_level` as [Sentry structured logs](/platforms/python/logs/) as long as the `enable_logs` experimental option is `True`.
+- `sentry_logs_level` (default `INFO`): The Sentry Python SDK will capture records with a level higher than or equal to `sentry_logs_level` as [Sentry structured logs](/platforms/python/logs/) as long as the `enable_logs` option is `True`.
 
   ```python
   sentry_sdk.init(

docs/platforms/python/integrations/loguru/index.mdx

@@ -68,17 +68,15 @@ logger.exception("An exception happened")
 - `"An exception happened"` will send the current exception from `sys.exc_info()` with the stack trace to Sentry. If there's no exception, the current stack will be attached.
 - The debug message `"I am ignored"` will not be captured by Sentry. To capture it, set `level` to `DEBUG` or lower in `LoguruIntegration`.
 
-Loguru log records can additionally also be captured as [Sentry logs](/platforms/python/logs/) as long as the `enable_logs` experimental option is `True`.
+Loguru log records can additionally also be captured as [Sentry logs](/platforms/python/logs/) as long as the `enable_logs` option is `True`.
 
 ```python
 import sentry_sdk
 from loguru import logger
 
 sentry_sdk.init(
     # ...
-    _experiments={
-        "enable_logs": True,
-    },
+    enable_logs=True,
 )
 
 logger.info("I will be sent to Sentry logs")
@@ -152,7 +150,7 @@ sentry_sdk.init(
 
   The Sentry Python SDK will capture log records with a level higher than or equal to `sentry_logs_level` as [Sentry structured logs](/platforms/python/logs/). If set to `None`, the SDK won't send records as logs.
 
-  To capture Loguru log records as Sentry logs, you must enable the experimental `enable_logs` option when initializing the SDK (regardless of the `sentry_logs_level` setting).
+  To capture Loguru log records as Sentry logs, you must enable the `enable_logs` option when initializing the SDK (regardless of the `sentry_logs_level` setting).
 
   ```python
   sentry_sdk.init(

platform-includes/logs/setup/python.mdx

@@ -1,4 +1,4 @@
-To enable logging, you need to initialize the SDK with the `_experiments["enable_logs"]` option set to `True`.
+To enable logging, you need to initialize the SDK with the `enable_logs` option set to `True`.
 
 ```python
 sentry_sdk.init(