[pull] main from getsentry:main - #409

…e chunks (#5852)

Prior to this commit, we'd always (rightly) bind originating process Proguard IDs to ANR events, but we'd (wrongly) bind current Proguard ID to ANR profile chunks. Usually the originating Proguard ID == the current Proguard ID, and so the discrepancy didn't matter. But the two differ in the situation when a user updates the host app after the ANR occurs but before it's reported. When that happens, deobfuscation for ANR profile chunks in the Sentry UI can break.

This commit ensures both the ANR event and the ANR profile chunk receive the same originating Proguard ID by:

1. having the entity that determines the originating Proguard ID (ApplicationExitInfoEventProcessor) pass that ID to the profile chunk pipeline; and

2. updating our DebugMeta.buildDebugMeta(ProfileChunk, ...) method so that the profile chunk pipeline honors (rather than clobbers) the Proguard ID the event processor bakes into the DebugMeta owned by the incoming profile chunk.

Gradle 9.6 deprecated four APIs our build scripts still used, all of
which either fail or are removed in Gradle 10:

- Project.getProperties, replaced with providers.gradleProperty
- Project objects as dependency notation, replaced with project(path)
- the 'val x by creating' configuration delegate, replaced with create()
- the 'val x by getting' source set delegate, replaced with getByName()

The remaining Gradle 10 warnings come from Detekt and AGP internals, not
from our scripts, so they can only be resolved by upgrading those.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>