build: Remove global per-test JVM heap cap

[runningcode]

Removes the global per-test JVM heap cap from the root build.gradle.kts:

// Cap JVM args per test
minHeapSize = "256m"
maxHeapSize = "2g"

This cap was applied to every module's test task via allprojects, but only one module actually needs it. CI confirmed that with the global cap removed, only :sentry-android-core:testReleaseUnitTest fails — with OutOfMemoryError: Java heap space, because Robolectric loads the android-all jar into each test JVM. Every other module passes on the JVM defaults.

The cap is therefore restored to just sentry-android-core's build.gradle.kts (via testOptions.unitTests.all { }), where it is actually required.

Note: due to the fact that some tests didn't run on this PR because they were cached, we might need to add this to more tests later.

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.46.0 (1)	release

⚙️ sentry-android Build Distribution Settings

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	353.92 ms	425.82 ms	71.90 ms
Size	0 B	0 B	0 B

Baseline results on branch: main

Startup times

Revision	Plain	With Sentry	Diff
abfcc92	337.38 ms	427.39 ms	90.00 ms
4e3e79d	369.55 ms	418.39 ms	48.83 ms
9054d65	330.94 ms	403.24 ms	72.30 ms
a416a65	316.52 ms	359.67 ms	43.15 ms
d15471f	315.61 ms	360.22 ms	44.61 ms
22f4345	325.23 ms	454.66 ms	129.43 ms
6b019b7	403.90 ms	546.09 ms	142.19 ms
d217708	409.83 ms	474.72 ms	64.89 ms
52feca7	314.77 ms	378.67 ms	63.90 ms
f634d01	375.06 ms	420.04 ms	44.98 ms

App size

Revision	Plain	With Sentry	Diff
abfcc92	1.58 MiB	2.13 MiB	557.31 KiB
4e3e79d	0 B	0 B	0 B
9054d65	1.58 MiB	2.29 MiB	723.38 KiB
a416a65	1.58 MiB	2.12 MiB	555.26 KiB
d15471f	1.58 MiB	2.13 MiB	559.54 KiB
22f4345	1.58 MiB	2.29 MiB	719.83 KiB
6b019b7	0 B	0 B	0 B
d217708	1.58 MiB	2.10 MiB	532.97 KiB
52feca7	0 B	0 B	0 B
f634d01	1.58 MiB	2.10 MiB	533.40 KiB

[sentry]

Bug: Removing the global maxHeapSize leaves four Robolectric-using modules without an explicit heap cap, risking OutOfMemoryError in their test tasks.
_{Severity: MEDIUM}

Suggested Fix

Apply explicit maxHeapSize settings to the testOptions.unitTests.all block for each of the affected modules: sentry-android-replay, sentry-compose, sentry-android-navigation, and sentry-android-distribution. A setting like maxHeapSize = "2g" would be consistent with the previous global configuration and the fix applied to sentry-android-core.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: build.gradle.kts#L105-L106

Potential issue: The removal of the global `maxHeapSize` setting in the root
`build.gradle.kts` leaves four modules that use Robolectric (`sentry-android-replay`,
`sentry-compose`, `sentry-android-navigation`, `sentry-android-distribution`) without an
explicit heap size configuration. These modules enable `isIncludeAndroidResources`,
which causes Robolectric to load the large `android-all` jar. Without a defined
`maxHeapSize`, their test tasks will rely on default JVM memory settings, which may be
insufficient and lead to `OutOfMemoryError` failures in the test environment,
particularly in CI or as test suites expand.

_{Did we get this right? 👍 / 👎 to inform future reviews.}