[lazerg]

Summary:

BundleHermesCTask always passes --reset-cache to the bundle command, and nothing in the react {} block can turn it off. Metro's default cache lives in os.tmpdir()/metro-cache, which every Metro on the machine shares. So each Android release bundle wipes the cache of other projects and dev servers, and on Windows it can fail with ENOTEMPTY when another Metro writes into that folder during the reset.

This adds a resetCache property to the react {} extension. It defaults to true, so builds work as before, and resetCache = false drops the flag from the bundle command.

Fixes #59543

Changelog:

[ANDROID] [ADDED] - Add resetCache to the react {} Gradle extension to let release bundles keep the Metro cache

Test Plan:

Added getBundleCommand_withResetCacheDisabled_returnsCommandWithoutResetCache to BundleHermesCTaskTest, and the existing command tests still expect --reset-cache by default. ./gradlew :react-native-gradle-plugin:test --tests 'com.facebook.react.tasks.BundleHermesCTaskTest' passes (17 tests), and ktfmt is clean on the changed files.

[lazerg]

The build_android failure isn't from this change. It also fails on main since the Kotlin 2.3.21 update (#59535): :gradle-plugin:shared:compileKotlin warns that API version 2.0 is deprecated, and -Werror turns that warning into an error.