fix(react-native) tracingOrigins was renamed to tracePropagationTargets (#6298)

Author: krystofwoldrich

src/platform-includes/performance/enable-tracing/react-native.mdx

@@ -12,7 +12,7 @@ Sentry.init({
 
   integrations: [
     new Sentry.ReactNativeTracing({
-      tracingOrigins: ["localhost", "my-site-url.com", /^\//],
+      tracePropagationTargets: ["localhost", "my-site-url.com", /^\//],
       // ... other options
     }),
   ],

src/platform-includes/performance/tracePropagationTargets-example/react-native.mdx

@@ -3,15 +3,15 @@ For example:
 - A frontend application is served from `example.com`
 - A backend service is served from `api.example.com`
 - The frontend application makes API calls to the backend
-- Therefore, the option needs to be configured like this: `new Sentry.ReactNativeTracing({tracingOrigins: ['api.example.com']})`
+- Therefore, the option needs to be configured like this: `new Sentry.ReactNativeTracing({tracePropagationTargets: ['api.example.com']})`
 - Now outgoing XHR/fetch requests to `api.example.com` will get the `sentry-trace` header attached
 
 ```javascript
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
   integrations: [
     new Sentry.ReactNativeTracing({
-      tracingOrigins: ["localhost", "my-site-url.com"],
+      tracePropagationTargets: ["localhost", "my-site-url.com"],
     }),
   ],