chore(scripts): improve bootstrap.js with npm fallback and clearer errors

[itspavant]

Brief Summary of Changes

Improved scripts/bootstrap.js developer experience:

• Detects if yarn is missing and provides a clear error message instead of failing silently.
• Adds a fallback path to run npm-equivalent bootstrap steps when Yarn is not installed, so contributors using npm are not blocked.
• Preserves existing behavior for Yarn users (yarn bootstrap still runs as before).
• Prints the exact command being executed for easier debugging.
• close Issue: Improve bootstrap.js to support both Yarn and NPM with clearer errors #50

What does this PR address?

• GitHub issue (Add reference - #XX)
• Refactoring
• New feature
• Bug fix
• Adds more tests

Are tests included?

• Yes
• No
  (The setup for this repo is non-trivial, so I did not run the full suite. This PR only modifies scripts/bootstrap.js, which is used for contributor setup, so it does not impact SDK runtime or published package behavior.)

Reviewer, please note:

• The repo’s package.json currently defines "bootstrap": "yarn example && yarn install".
  If Yarn is not installed, the updated script translates this to equivalent npm commands:
  1. npm --prefix example install
  2. npm install (root)
• This ensures contributors without Yarn can still set up the repo.
• If maintainers prefer to enforce Yarn-only usage, the npm fallback part can be removed, leaving only the clearer error messages.

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I ran the full test suite before pushing the changes and all the tests pass.
  (Not run due to complexity, but the change is isolated to the bootstrap script and does not affect published code.)

[itspavant]

Dear Maintainers,

Please review the PR and let me know if you need any more modifications

Thank you.

[adimiz1]

Thanks for taking the time to improve the bootstrap experience! 👍 I appreciate the effort to support both yarn and npm users with better error messages.
However, I have some concerns about the current approach:
Complexity
The script has grown from ~29 lines to ~132 lines (4.5x increase). While the npm fallback is valuable, this adds significant maintenance burden for what should be a simple bootstrap script.
Potential Logic Issue
There appears to be a bug in the fallback logic. After the yarn bootstrap attempt, this block runs:

  // package.json.bootstrap = "yarn example && yarn install"
  // npm-equivalent:
  // 1) npm --prefix ./example install
  // 2) npm install (root)
  // run step 1
  const step1 = runSync('npm', ['--prefix', 'example', 'install'], options);
  if (step1.status !== 0) {
    console.error('Failed to install dependencies in ./example using npm.');
    process.exit(step1.status);
  }
  // run step 2
  const step2 = runSync('npm', ['install'], options);

This block will execute whenever hasNpm is true, even if yarn bootstrap succeeded. This means both yarn AND npm could run installations, which is wasteful and could cause issues.
Also:

  // run yarn bootstrap
  result = runSync('yarn', ['bootstrap'], options);
  // If yarn bootstrap fails but npm exists, try npm equivalent as fallback
  if (result.status !== 0 && hasNpm) {
    console.warn('yarn bootstrap failed; attempting npm-equivalent bootstrap...');
    // fall through to npm-equivalent
  }

If yarn fails for a legitimate reason (network issues, package conflicts, etc.), silently falling back to npm could mask the real problem and make debugging harder.