docs(python-sdk): add more granularity to types (#12620)

Author: stephanie-anderson

docs/platforms/python/configuration/options.mdx

@@ -141,23 +141,23 @@ The `project_root` is used to mark frames in a stack trace either as being in yo
 
 </SdkOption>
 
-<SdkOption name="in_app_include" type='list' defaultValue='[]'>
+<SdkOption name="in_app_include" type='list[str]' defaultValue='[]'>
 
 A list of string prefixes of module names that belong to the app. This option takes precedence over `in_app_exclude`.
 
 Sentry differentiates stack frames that are directly related to your application ("in application") from stack frames that come from other packages such as the standard library, frameworks, or other dependencies. The application package is automatically marked as `inApp`. The difference is visible in [sentry.io](https://sentry.io), where only the "in application" frames are displayed by default.
 
 </SdkOption>
 
-<SdkOption name="in_app_exclude" type='list' defaultValue='[]'>
+<SdkOption name="in_app_exclude" type='list[str]' defaultValue='[]'>
 
 A list of string prefixes of module names that do not belong to the app, but rather to third-party packages. Modules considered not part of the app will be hidden from stack traces by default.
 
 This option can be overridden using <PlatformIdentifier name="in_app_include" />.
 
 </SdkOption>
 
-<SdkOption name="max_request_body_size" type='string' defaultValue='medium'>
+<SdkOption name="max_request_body_size" type='str' defaultValue='medium'>
 
 This parameter controls whether integrations should capture HTTP request bodies. It can be set to one of the following values:
 
@@ -195,13 +195,13 @@ Set this boolean to `False` to disable sending of client reports. Client reports
 
 ## Integration Configuration
 
-<SdkOption name="integrations" defaultValue='[]'>
+<SdkOption name="integrations" type='list[sentry_sdk.integrations.Integration]' defaultValue='[]'>
 
 List of integrations to enable in addition to [auto-enabling integrations](/platforms/python/integrations). This setting can be used to override the default config options for a specific auto-enabling integration or to add an integration that is not auto-enabled.
 
 </SdkOption>
 
-<SdkOption name="disabled_integrations" defaultValue='None'>
+<SdkOption name="disabled_integrations" type='list[sentry_sdk.integrations.Integration]' defaultValue='[]'>
 
 List of integrations that will be disabled. This setting can be used to explicitly turn off specific [auto-enabling](/platforms/python/integrations/#available-integrations) or [default](/platforms/python/integrations/default-integrations/) integrations.
 </SdkOption>
@@ -250,7 +250,7 @@ The callback typically gets a second argument (called a "hint") which contains t
 
 Transports are used to send events to Sentry. Transports can be customized to some degree to better support highly specific deployments.
 
-<SdkOption name="transport" defaultValue='None'>
+<SdkOption name="transport" type='sentry_sdk.transport.Transport' defaultValue='None'>
 
   Switches out the transport used to send events. How this works depends on the SDK. It can, for instance, be used to capture events for unit-testing or to send it through some more complex setup that requires proxy authentication.
 
@@ -272,7 +272,7 @@ Configures a separate proxy for outgoing HTTPS requests. This value might not be
 
 </SdkOption>
 
-<SdkOption name="proxy_headers" type='dict' defaultValue='None'>
+<SdkOption name="proxy_headers" type='dict[str, str]' defaultValue='None'>
 
 A dict containing additional proxy headers (usually for authentication) to be forwarded to `urllib3`'s [`ProxyManager`](https://urllib3.readthedocs.io/en/1.24.3/reference/index.html#urllib3.poolmanager.ProxyManager).
 
@@ -349,7 +349,7 @@ If <PlatformIdentifier name="trace_propagation_targets" /> is not provided, trac
 
 </SdkOption>
 
-<SdkOption name="functions_to_trace" type='list' defaultValue='[]'>
+<SdkOption name="functions_to_trace" type='list[str]' defaultValue='[]'>
 
 An optional list of functions that should be set up for tracing. For each function in the list, a span will be created when the function is executed.
 Functions in the list are represented as strings containing the fully qualified name of the function.