perf(user-interactions): Make user interaction tracing faster and allocate less

[romtsn]

📜 Description

• Use class.getName instead of class.getCanonicalName as it's almost ~2x faster, and there's almost no difference in what it returns except for inner classes (tested 10k iterations over 10 times)

• Fix SentryTag extraction for compose, because SentryTagModifierNodeElement is an inner class and we have to use a dollar-sign to properly get its class name.

• Use fori instead of foreach loop to avoid allocating an Iterator in hot paths (e.g. when traversing the view hierarchy which can happen 100s of times for complex UIs). Reduced allocations by almost 2x doing the same user flow (launch -> scroll -> button click)

Before

After

💡 Motivation and Context

Improve perf of user interaction tracing

💚 How did you test it?

existing tests

📝 Checklist

• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

[markushi]

🙏 👏

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	420.12 ms	484.44 ms	64.32 ms
Size	1.58 MiB	2.08 MiB	507.26 KiB

Previous results on branch: rz/perf/faster-gesture-tracking

Startup times

Revision	Plain	With Sentry	Diff
148e92b	442.19 ms	539.20 ms	97.01 ms

App size

Revision	Plain	With Sentry	Diff
148e92b	1.58 MiB	2.08 MiB	507.26 KiB