fix(native): Update notes on Native perf support (#7457)

src/platforms/common/performance/index.mdx

@@ -74,6 +74,16 @@ First, enable tracing and configure the sampling rate for transactions. Set the
 
 The two options are meant to be mutually exclusive. If you set both, <PlatformIdentifier name="traces-sampler" /> will take precedence.
 
+<PlatformSection supported={["native"]}>
+
+<Alert level="info">
+
+The Native SDK doesn't currently support sampling functions (<PlatformIdentifier name="traces-sampler" />).
+
+</Alert>
+
+</PlatformSection>
+
 <PlatformContent includePath="performance/configure-sample-rate" />
 
 Learn more about how the options work in <PlatformLink to="/configuration/sampling/">Sampling Transactions</PlatformLink>.
@@ -102,6 +112,16 @@ If you leave your sample rate at `1.0`, a transaction will be sent every time a
 
 </PlatformSection>
 
+<PlatformSection supported={["native"]}>
+
+<Alert level="info">
+
+The Native SDK doesn't currently support sampling functions (<PlatformIdentifier name="traces-sampler" />).
+
+</Alert>
+
+</PlatformSection>
+
 <PlatformSection supported={["javascript.react"]}>
 
 `@sentry/react` exports a `withProfiler` higher order component that can be used to capture React related spans for specific React components.

src/platforms/common/performance/instrumentation/custom-instrumentation.mdx

@@ -37,16 +37,6 @@ To capture transactions customized to your organization's needs, you must first
 
 </Note>
 
-<PlatformSection supported={["native"]}>
-
-<Note>
-
-Performance monitoring is still an experimental, work-in-progress feature, and its API may be unstable. It may also have bugs. Feedback is appreciated, and should be submitted as an issue in the repository linked on the right side of this page.
-
-</Note>
-
-</PlatformSection>
-
 To instrument certain regions of your code, you can create transactions to capture them.
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />