Fix issue title on Android when a wrapped RuntimeException is thrown by the system

[markushi]

📜 Description

Based on #3184, as a quick fix we want to reverse the order (similar to e.g. RN) of the exception list. This applies to Android only, and only to RuntimeExceptions.

💡 Motivation and Context

Improve getsentry/sentry#64074

💚 How did you test it?

Added unit tests, did a quick manual test with our demo app.

📝 Checklist

• I reviewed the submitted code.
• 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.
• 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

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	393.32 ms	438.52 ms	45.20 ms
Size	1.70 MiB	2.27 MiB	586.43 KiB

Baseline results on branch: main

Startup times

Revision	Plain	With Sentry	Diff
1ae2ec6	353.85 ms	419.71 ms	65.85 ms
99a51e2	405.11 ms	479.65 ms	74.54 ms
1f3652d	361.62 ms	424.76 ms	63.14 ms
86f0096	371.86 ms	439.78 ms	67.92 ms
8fd337b	349.16 ms	459.22 ms	110.06 ms
8ff8fd0	432.77 ms	495.18 ms	62.41 ms
7eccfdb	366.98 ms	440.27 ms	73.29 ms
95a98b5	379.14 ms	420.80 ms	41.66 ms
d6d2b2e	463.14 ms	545.56 ms	82.42 ms
8838e01	367.65 ms	447.40 ms	79.75 ms

App size

Revision	Plain	With Sentry	Diff
1ae2ec6	1.70 MiB	2.27 MiB	584.63 KiB
99a51e2	1.72 MiB	2.29 MiB	576.34 KiB
1f3652d	1.72 MiB	2.27 MiB	554.95 KiB
86f0096	1.72 MiB	2.29 MiB	576.50 KiB
8fd337b	1.72 MiB	2.27 MiB	555.00 KiB
8ff8fd0	1.72 MiB	2.27 MiB	558.15 KiB
7eccfdb	1.72 MiB	2.27 MiB	556.93 KiB
95a98b5	1.70 MiB	2.27 MiB	586.31 KiB
d6d2b2e	1.72 MiB	2.27 MiB	555.05 KiB
8838e01	1.72 MiB	2.29 MiB	578.15 KiB

Previous results on branch: fix/android-runtime-exception-title

Startup times

Revision	Plain	With Sentry	Diff
2929a36	382.12 ms	466.60 ms	84.48 ms

App size

Revision	Plain	With Sentry	Diff
2929a36	1.70 MiB	2.27 MiB	586.43 KiB

[romtsn]

LGTM, I hope we can figure this out on the backend side somehow in the future