Add --out-to-build option

[kraenhansen]

As a quick fix to address the issue of the output directory being misaligned with cmake-js and node-gyp (mentioned in #146).

Merging this PR will:

• Introduce a --out-to-build option which will output the prebuild artifact in the build directory (under "build/Release" or "build/Debug"), just like cmake-js and node-gyp does.

We might want to make this the default behaviour at some point.

[Copilot]

Pull Request Overview

This PR adds a new --out-to-build CLI flag so that artifacts are placed under build/<configuration>, mirroring cmake-js and node-gyp, and renames the existing outPathOption variable while adding logic to ensure --out and --out-to-build are mutually exclusive.

• Introduce --out-to-build option in cli.ts
• Rename outPathOption variable to outOption
• Add runtime assertion to prevent using --out with --out-to-build

Comments suppressed due to low confidence (2)

packages/cmake-rn/src/cli.ts:82

• [nitpick] Renaming outPathOption to outOption reduces clarity and consistency. Consider reverting to outPathOption or using outDirOption to more clearly describe its purpose.

const outOption = new Option(

packages/cmake-rn/src/cli.ts:178

• There are no tests verifying the new --out-to-build behavior or its conflict with --out. Adding unit tests for both the default and conflict scenarios will help prevent regressions.

      if (globalContext.outToBuild) {

[Copilot]

Instead of manually asserting mutual exclusion at runtime, use Commander.js's .conflicts() API to declare that --out and --out-to-build cannot be used together, providing built-in CLI validation and clearer error messaging.

[kraenhansen]

We'll want to make this the default behavior and as such, I expect it to just end up as default for the --out parameter.

[kraenhansen]

Closing as superseded by #150