fix: add support for resolving Viro Android path in workspace environments

[busybox11]

Summary

Currently, Viro's Expo config plugin hardcodes ../node_modules/@reactvision/react-viro/android/... when writing the Android project paths into settings.gradle. This assumes react-viro is installed in the app's own node_modules.

In a monorepo (pnpm/yarn/npm/... workspace), the package is hoisted to the workspace root instead, so those paths don't exist and the Gradle build fails with:

Configuring project ':gvr_common' without an existing directory is not allowed.
The configured projectDirectory '.../apps/<app>/node_modules/@reactvision/react-viro/android/gvr_common' does not exist

What changed

I have added support for resolving react-viro's real install location instead of assuming it's app-local.

withViroSettingsGradle now uses require.resolve("@reactvision/react-viro/package.json", { paths: [projectRoot] }) and emits the path relative to the Android project root.

If resolution fails it falls back to the original ../node_modules/... string, so nothing changes for flat installs.

Why this is helpful

• Fixes prebuild/build for anyone using Viro inside a monorepo with hoisted dependencies.
• No behavior change for standard (non-workspace) projects — the resolved path collapses back to ../node_modules/@reactvision/react-viro/android.

Testing

• tsc --noEmit passes.
• Flat install → resolves to ../node_modules/@reactvision/react-viro/android (unchanged).
• pnpm monorepo → resolves to the hoisted root path, and the target directories exist.

---

This PR was made against develop to make sure that there wasn't already a fix in the works. Can reopen against main instead, feel free to let me know if this is necessary.