android: inject ExecOperations for Gradle 9 compatibility

[kraenhansen]

Targets the kh/adopt-static-h-node-api branch (PR #372).

Problem

RN 0.87 (adopted in #372) bumps the Gradle wrapper to 9.x, which removed Project.exec(). The linkNodeApiModules task in packages/host/android/build.gradle calls the bare exec {} closure inside its doLast action, so on Gradle 9 every Android build fails at configuration/execution with:

Execution failed for task ':react-native-node-api:linkNodeApiModules'.
> Could not find method exec() for arguments [...] on task ':react-native-node-api:linkNodeApiModules' of type org.gradle.api.DefaultTask.

On the #372 branch this reddened every unit-test lane (gradle.test.ts builds this module on ubuntu/macOS/windows) as well as the Test app (Android) job.

Fix

Use the Gradle 9 supported replacement: inject the ExecOperations service via an @Inject-annotated interface and call injectedExecOps.execOps.exec {} instead of the removed Project.exec().

interface InjectedExecOps {
  @Inject
  ExecOperations getExecOps()
}
def injectedExecOps = project.objects.newInstance(InjectedExecOps)

The command line, streams and environment passed to exec are unchanged.

Test plan

• CI on the Adopt Hermes' first-party Node-API (static_h) #372 branch: the three Unit tests lanes go green (gradle.test.ts builds the Android module successfully).
• Test app (Android) gets past the linkNodeApiModules failure (remaining Android e2e work is still tracked on Adopt Hermes' first-party Node-API (static_h) #372).

Native Android build isn't runnable on the CI-less Linux worker this was authored on, so the Gradle behaviour is verified by the #372 branch's CI rather than locally.

---

Generated by Claude Code