Python: Getting Started gnu backtrace (#7863)

* Python: Getting Started gnu backtrace

* style(lint): Auto commit lint changes

* Update src/platforms/python/common/configuration/integrations/gnu_backtrace.mdx

Co-authored-by: Shana Matthews <shana.l.matthews@gmail.com>

---------

Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
Co-authored-by: Shana Matthews <shana.l.matthews@gmail.com>

src/platforms/python/common/configuration/integrations/gnu_backtrace.mdx

@@ -4,20 +4,14 @@ description: "Learn about the GNU backtrace integration and how to add it to you
 sidebar_order: 50
 ---
 
-<!-- NOTE: Due to being in common, redirects are in vercel.json -->
-
 The GNU backtrace integration parses native stack trace produced by [`backtrace_symbols`](https://linux.die.net/man/3/backtrace_symbols) from error messages and concatenates them with the Python traceback.
 
 It is currently tested to work with server exceptions raised by [`clickhouse-driver`](https://github.com/mymarilyn/clickhouse-driver).
 
-<Note>
-
-**This integration is experimental.** It may be removed in minor versions. When enabling this integration, expect to see new event groups due to new stack trace frames.
-
-</Note>
-
 ## Install
 
+Install `sentry-sdk` from PyPI.
+
 ```bash
 pip install --upgrade 'sentry-sdk'
 ```
@@ -39,3 +33,9 @@ sentry_sdk.init(
  ],
 )
 ```
+
+## Verify
+
+The GNU backtrace integration is tested with server exceptions raised by [`clickhouse-driver`](https://github.com/mymarilyn/clickhouse-driver).
+
+Other libraries must emit exceptions that have backtrace-compatible values for the GNU backtrace integration to parse the exceptions.