Adding sentryTag in compose docs (#10051)

* Replace testTag with sentryTag

* Add testTag again

Author: StefMa

docs/platforms/android/integrations/jetpack-compose/index.mdx

@@ -38,7 +38,7 @@ Once performance metrics have been enabled, you'll see two spans inside your tra
 - `ui.compose.composition`, describing the time it took to execute your `@Composable`
 - `ui.compose.rendering`, describing the time it took to render your `@Composable` to the canvas
 
-The `SentryTraced` function also provides an `enableUserInteractionTracing` argument, which automatically applies a `Modifier.testTag()` and enables the _User Interactions_ feature mentioned below.
+The `SentryTraced` function also provides an `enableUserInteractionTracing` argument, which automatically applies a `Modifier.sentryTag()` and enables the _User Interactions_ feature mentioned below.
 
 ### Installation
 
@@ -110,17 +110,20 @@ SentryAndroid.init(this) { options ->
 }
 ```
 
-The Sentry SDK utilizes the built-in `Modifier.testTag("<tag>")` of a Composable to determine its identifier. Here's an example:
+#### Capture Composables
+
+The Sentry SDK requires you to have either `Modifier.sentryTag("<tag>")` or `Modifier.testTag("<tag>")` applied on each `@Composable` you want to capture to determine its identifier.
+Here's an example:
 
 ```kotlin
-import androidx.compose.ui.platform.testTag
+import io.sentry.compose.sentryTag
 
 @Composable
 fun LoginScreen() {
   Column {
     // ...
     Button(
-        modifier = Modifier.testTag("button_login"),
+        modifier = Modifier.sentryTag("button_login"),
         onClick = { TODO() }) {
         Text(text = "Login")
     }
@@ -130,7 +133,8 @@ fun LoginScreen() {
 
 <Note>
 
-If a `@Composable` doesn't have a `testTag` modifier applied, both breadcrumbs and transactions won't be captured because they can't be uniquely identified. To automatically generate tags, refer to the docs about our <PlatformLink to="/enhance-errors/kotlin-compiler-plugin/">Sentry Kotlin Compiler Plugin</PlatformLink>.
+If a `@Composable` doesn't have a `.sentryTag` or a `.testTag` modifier applied, both breadcrumbs and transactions won't be captured because they can't be uniquely identified.
+To automatically generate tags, refer to the docs about our <PlatformLink to="/enhance-errors/kotlin-compiler-plugin/">Sentry Kotlin Compiler Plugin</PlatformLink>.
 
 </Note>
 

docs/platforms/android/performance/instrumentation/automatic-instrumentation.mdx

@@ -278,17 +278,18 @@ If the view doesn't have the `id` assigned, the transaction won't be captured be
 
 _(New in version 6.10.0)_
 
-The SDK composes the transaction name out of the host `Activity` and the `tag` set by way of the `Modifier.testTag("<tag>")` of the `Composable` (for example, `LoginActivity.login_button`). The transaction operation is set to `ui.action` plus the interaction type (one of `click`, `scroll`, or `swipe`).
+The SDK composes the transaction name out of the host `Activity` and the `tag` set by way of the `Modifier.sentryTag("<tag>")` of the `Composable` (for example, `LoginActivity.login_button`). 
+The transaction operation is set to `ui.action` plus the interaction type (one of `click`, `scroll`, or `swipe`).
 
 ```kotlin
-import androidx.compose.ui.platform.testTag
+import io.sentry.compose.sentryTag
 
 @Composable
 fun LoginScreen() {
   Column {
     // ...
     Button(
-        modifier = Modifier.testTag("button_login"),
+        modifier = Modifier.sentryTag("button_login"),
         onClick = { TODO() }) {
         Text(text = "Login")
     }
@@ -298,7 +299,8 @@ fun LoginScreen() {
 
 <Note>
 
-If the `@Composable` doesn't have a `testTag` modifier applied, the transaction won't be captured because it can't be uniquely identified. To capture a transaction for the `@Composable`, you must either add a `testTag` modifier or enable automatic `@Composable` tagging.
+If the `@Composable` doesn't have a `sentryTag` modifier applied, the transaction won't be captured because it can't be uniquely identified. 
+To capture a transaction for the `@Composable`, you must either add a `sentryTag` modifier or enable automatic `@Composable` tagging.
 
 </Note>
 
@@ -310,7 +312,9 @@ The Sentry Kotlin Compiler plugin is considered _experimental_. Give it a try an
 
 </Note>
 
-The <PlatformLink to="/enhance-errors/kotlin-compiler-plugin/">Sentry Kotlin Compiler Plugin</PlatformLink> can automatically enrich your `@Composable` functions during compilation with a tag name, based on the function name of your `@Composable`. In order to use this feature, the Sentry Kotlin Compiler plugin needs to be applied to all modules, which contain `@Composable` elements.
+The <PlatformLink to="/enhance-errors/kotlin-compiler-plugin/">Sentry Kotlin Compiler Plugin</PlatformLink> can automatically enrich your `@Composable` functions during compilation with a tag name, 
+based on the function name of your `@Composable`. 
+In order to use this feature, the Sentry Kotlin Compiler plugin needs to be applied to all modules, which contain `@Composable` elements.
 
 ```groovy {filename:app/build.gradle}
 plugins {