test(e2e): Scroll TurboModule attribute block into view on Android

The `turbo_module.*` attribute block is the last content in a long
ScrollView, so on the shorter Android emulator screen it renders below
the fold. `assertVisible` only inspects the current viewport, so the
`turbo_module.total_call_count: 6` assertion has failed on every Android
REV2 run since #6549 introduced the test, while iOS (taller screen, block
in view) has been green — proving the SDK and on-device render are correct.

Scroll the block into view before asserting, and match the full line with
a regex (Maestro anchors `assertVisible` text to the whole node, so a bare
`total_call_count:` prefix would not match `... : 6`). The exact on-screen
count is intentionally not pinned — it can race the async `getPlatform`
record settling against the synchronous post-`end()` read; the authoritative
counts are asserted against the transaction envelope in
turboModuleSpanAttributes.test.ts.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: antonis

samples/react-native/e2e/tests/turboModuleSpanAttributes/turboModuleSpanAttributes.test.yml

@@ -32,8 +32,30 @@ appId: io.sentry.reactnative.sample
 
 # The `turbo_module.*` attributes the TurboModuleContext integration attached
 # to the root span are rendered on screen so QA can eyeball them on device.
-- assertVisible: 'turbo_module.total_call_count: 6'
-- assertVisible: 'turbo_module.total_error_count: 0'
+# This block is the LAST content in a long ScrollView, so on the shorter Android
+# emulator screen it starts below the fold — scroll it into view before asserting
+# (`assertVisible` alone only sees the current viewport, which is why this never
+# passed on Android since #6549).
+#
+# Match the full line with a regex: Maestro anchors `assertVisible` text to the
+# whole node, so a bare `total_call_count:` prefix would NOT match `... : 6`.
+# We deliberately don't pin the exact on-screen count here — it can race the
+# async `getPlatform` record settling relative to the synchronous post-`end()`
+# read. The exact aggregate counts are asserted against the transaction envelope
+# in turboModuleSpanAttributes.test.ts, which is the authoritative source.
+- scrollUntilVisible:
+    element:
+      text: 'turbo_module.total_call_count: .*'
+    direction: DOWN
+    timeout: 10000
+# Sorted alphabetically, `total_error_count` renders a few lines below
+# `total_call_count`, so it may sit past the bottom edge after the scroll above —
+# scroll to it independently rather than assume both fit in one viewport.
+- scrollUntilVisible:
+    element:
+      text: 'turbo_module.total_error_count: 0'
+    direction: DOWN
+    timeout: 10000
 
 # A native throw surfaced to JS must still be capturable (crash-context path)
 - tapOn: 'Throw from native platform'