feat(python): Add sentry_logs_level option to Loguru, logging integration (#14015)

## DESCRIBE YOUR PR
Since we started supporting Sentry logs via the logging integration (and
more recently Loguru), we haven't added the new `sentry_logs_level`
option used to fine-tune which logs should be captured. Adding it here.

Direct links to preview:
-
[logging](https://sentry-docs-git-ivana-pythonsentry-logs-level.sentry.dev/platforms/python/integrations/logging/#options)
-
[Loguru](https://sentry-docs-git-ivana-pythonsentry-logs-level.sentry.dev/platforms/python/integrations/loguru/#options)

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [ ] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [x] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

---------

Co-authored-by: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com>

Author: sentrivana

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

@@ -72,8 +72,9 @@ sentry_sdk.init(
     # ...
     integrations=[
         LoggingIntegration(
-            level=logging.INFO,        # Capture info and above as breadcrumbs
-            event_level=logging.INFO   # Send records as events
+            level=logging.INFO,              # Capture INFO and above as breadcrumbs
+            event_level=logging.ERROR,       # Send ERROR records as events
+            sentry_logs_level=logging.INFO,  # Capture INFO and above as logs
         ),
     ],
 )
@@ -85,6 +86,15 @@ 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 logs as long as the `enable_logs` experimental option is `True`:
+
+  ```python
+  sentry_sdk.init(
+      # ...
+      _experiments={"enable_logs": True},
+  )
+  ```
+
 <Alert title="Note">
 
 The Sentry Python SDK will honor the configured level of each logger (set with `logger.setLevel(level)` or `logging.basicConfig(level=level)`). That means that you will not see any `INFO` or `DEBUG` events from a logger with the level set to `WARNING`, regardless of how you configure the integration. If not set explicitly, the logging level defaults to `WARNING`.

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

@@ -108,15 +108,14 @@ from loguru import logger
 from sentry_sdk.integrations.loguru import LoguruIntegration
 from sentry_sdk.integrations.loguru import LoggingLevels
 
-sentry_loguru = LoguruIntegration(
-    level=LoggingLevels.INFO.value,        # Capture info and above as breadcrumbs
-    event_level=LoggingLevels.ERROR.value  # Send errors as events
-)
-
 sentry_sdk.init(
     # ...
     integrations=[
-        sentry_loguru,
+        LoguruIntegration(
+            level=LoggingLevels.INFO.value,              # Capture INFO and above as breadcrumbs
+            event_level=LoggingLevels.ERROR.value,       # Send ERROR logs as events
+            sentry_logs_level=LoggingLevels.INFO.value,  # Capture INFO and above as logs
+        )
     ],
 )
 ```
@@ -133,6 +132,22 @@ sentry_sdk.init(
 
   Default: `ERROR`
 
+- `sentry_logs_level`
+
+  The Sentry Python SDK will capture log records with a level higher than or equal to `sentry_logs_level` as 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).
+
+  ```python
+  sentry_sdk.init(
+      # ...
+      _experiments={"enable_logs": True},
+  )
+  ```
+
+  Default: `INFO`
+
+
 ## Supported Versions
 
 - Loguru: 0.5+