Adding sentryTag in compose docs

[StefMa]

DESCRIBE YOUR PR

Changed the docs from mentioning Modifier.testTag to Modifier.sentryTag.
I'm not sure why the testTag thing is there, if this was changed to your own tag or what..
I just found out that you actually use a custom sentryTag and not the testTag.
See https://github.com/getsentry/sentry-android-gradle-plugin/blob/1c15d184114b41058f3c0803c8675b79073f0d0a/sentry-kotlin-compiler-plugin/src/main/kotlin/io/sentry/compose/JetpackComposeTracingIrExtension.kt#L92

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• Urgent deadline (GA date, etc.):
• Other deadline:
• None: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
  Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

@StefMa is attempting to deploy a commit to the Sentry Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sentry-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 28, 2024 6:37pm

[vivianyentran]

@markushi Do you know if testTag was there for a reason?

[markushi]

@StefMa thanks for opening up this PR! Yes this is outdated information, as .sentryTag() didn't exist in our initial release. But both .testTag() and .sentryTag() should work: See the implementation for more details.

[StefMa]

Thanks for the clarification @markushi.
I have committed the changes you suggested.

But let me ask a question:
Would you be more interested in using a sentryTag instead of a testTag? 🤔
Because depending on your answer, we might want to document the testTag as legacy support and focus more on the sentryTag.
However, the advantage of using a testTag is that it doesn't require an additional dependency.

[StefMa]

@markushi can we get this merged? 😇

[markushi]

Would you be more interested in using a sentryTag instead of a testTag? 🤔

I think this highly depends on your use case, and thus we don't prefer one over the other. E.g. if you heavily use .testTag() already, there's no advantage of "polluting" your code with .sentryTag(). On the other hand, using .sentryTag() makes the usage of the tag more clear.