ref(sveltekit): Clarify limitations of auto instrumentation for Kit<2.31.0 (#15592)

Clarify that auto instrumentation will not work correctly if a SvelteKit
versions below 2.31.0 are used. This came up in
getsentry/sentry-javascript#18247.

Note: I intentionally opted not to show the `--import` alternative I
mentioned in the issue because it would be a 3rd (already outdated) way
of setting up the SDK. Furthermore, success would vary greatly based on
the used Kit adapter and deployment platform.

Author: Lms24

platform-includes/getting-started-complete/javascript.sveltekit.mdx

@@ -9,18 +9,22 @@ You need:
 
 <Expandable title="I'm on an older SvelteKit version than 2.31.0">
 
-Version `2.31.0` of SvelteKit introduces [official support for observability and tracing](https://svelte.dev/docs/kit/observability). This means that Sentry can now follow the official best practice for how the SDK should be set up.
-For you, this means:
+Version `2.31.0` of SvelteKit introduces [official support for observability and tracing](https://svelte.dev/docs/kit/observability). 
+This means that Sentry can now follow the official best practice for how the SDK should be set up:
 
-- The Sentry SDK will be initialized at the correct, earliest possible time on the server, allowing for all its auto-instrumentation to work correctly.
-- The Sentry SDK picks up spans emitted from SvelteKit directly. You'll get more accurate insights into the performance of your handlers, server actions, `load`, and remote functions.
+- The Sentry SDK will be initialized at the correct, earliest possible time on the server, allowing for all its auto-instrumentation to work correctly. 
+  This means, you will now get spans from auto instrumentation (e.g. database queries) automatically. 
+- The Sentry SDK picks up spans emitted from SvelteKit directly. 
+  You'll get more accurate insights into the performance of your handlers, server actions, `load`, and remote functions.
 
 SvelteKit observability is still an experimental feature in SvelteKit 2.x, but we recommend giving it a try.
 The Sentry wizard, as well as this guide, will use it as the default way of setting up the SDK.
 
 <PlatformSection notSupported={["javascript.cloudflare"]}>
 
-If you've already set up the SDK and don't want to migrate to the new setup, or don't want to upgrade to SvelteKit `2.31.0` or higher, that's fine too. Just follow [this guide](../manual-setup__v10.7.0) instead.
+If you've already set up the SDK and don't want to migrate to the new setup, or don't want to upgrade to SvelteKit `2.31.0` or higher, that's fine too. 
+Just follow <PlatformLink to="/manual-setup__v10.7.0">this guide</PlatformLink> instead. 
+However, note that auto instrumentation (e.g. for database queries) will not work.
 
 </PlatformSection>
 

platform-includes/getting-started-prerequisites/javascript.sveltekit.mdx

@@ -9,15 +9,20 @@ You need:
 
 <Expandable title="I'm on an older SvelteKit version than 2.31.0">
 
-Version `2.31.0` of SvelteKit, introduces [official support for observability and tracing](https://svelte.dev/docs/kit/observability). This means that Sentry can now follow the official best practise for how the SDK should be set up.
-For you this means:
-- The Sentry SDK will be initialized at the correct, earliest possible time on the server, allowing for all its auto instrumentation to work correctly.
-- The Sentry SDK picks up spans emitted from SvelteKit directly. You'll get more accurate insights into the performance of your handlers, server actions, `load` and remote functions.
+Version `2.31.0` of SvelteKit introduces [official support for observability and tracing](https://svelte.dev/docs/kit/observability). 
+This means that Sentry can now follow the official best practice for how the SDK should be set up:
 
-SvelteKit observability is still an experimental feature in SvelteKit 2.x but we recommend giving it a try. 
-The Sentry wizard, as well as our guides, will use it as the default way of setting up the SDK.
+- The Sentry SDK will be initialized at the correct, earliest possible time on the server, allowing for all its auto-instrumentation to work correctly. 
+  This means, you will now get spans from auto instrumentation (e.g. database queries) automatically. 
+- The Sentry SDK picks up spans emitted from SvelteKit directly. 
+  You'll get more accurate insights into the performance of your handlers, server actions, `load`, and remote functions.
 
-If you've already set up the SDK and don't want to migrate to the new setup, or don't want to upgrade to SvelteKit `2.31.0` or higher, that's fine too. Nothing will change for you!   
+SvelteKit observability is still an experimental feature in SvelteKit 2.x, but we recommend giving it a try.
+The Sentry wizard, as well as this guide, will use it as the default way of setting up the SDK.
+
+If you've already set up the SDK and don't want to migrate to the new setup, or don't want to upgrade to SvelteKit `2.31.0` or higher, that's fine too. 
+Just follow <PlatformLink to="/manual-setup__v10.7.0">this guide</PlatformLink> instead. 
+However, note that auto instrumentation (e.g. for database queries) will not work.  
 
 </Expandable>