test(android): add proguard tombstone test cases

[supervacuus]

📜 Description

This PR sits on top of #5116, but I added it separately because it addresses a different topic: tombstone frames that are ProGuard-obfuscated.

• The tests only check if the obfuscated frames affect the baseline (and I record a different set of Java frames for the snapshot).
• I also modified the build script of the Android sample, so I actually get meta properties for a release build, so I can upload ProGuard mappings for the sample.

The former should be merged into master. We don't have to merge the latter to master, but I think it will be could be useful for @markushi in https://linear.app/getsentry/issue/ANDROID-265/improve-ux-for-mixed-stacktraces (getsentry/sentry#107318), because it allows cross-checking UI changes for proguard.

The PR also allows us to verify that the ProGuard debug-meta is correctly appended to tombstone and ANR events when a corresponding properties file exists in the APK. If a mapping file has been uploaded with sentry-cli or the SAGP, the backend correctly triggers ProGuard deobfuscation, but it only deobfuscates the module, not the function:

Not sure if that is expected behavior (event).

#skip-changelog
(since this is currently only an internal test addition)

💡 Motivation and Context

💚 How did you test it?

📝 Checklist

• I added GH Issue ID & Linear ID
• 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