Build: Fix React Native sandbox generation under age gate

[ndelangen]

Closes https://github.com/storybookjs/storybook/actions/runs/32093433272/job/95580068842

What I did

Fixes the scheduled Generate and publish sandboxes workflow failures for the two React Native Web + Vite templates blocked by the 7-day package age gate:

• react-native-web-vite/expo-ts: add multitars to the Yarn/npm allowlist. Expo depends on it transitively, and recent releases fall inside the gate window.
• react-native-web-vite/rn-cli-ts: add a React Native allowlist and write a scratch .npmrc with min-release-age-exclude during scaffold so npx @react-native-community/cli init can download @react-native-community/template while the gate stays enabled for everything else.
• Bump the sandbox workflow npm floor to 11.17.0, which is when npm gained min-release-age-exclude.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

Caution

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

No manual UI testing is needed. To verify end-to-end, re-run the Generate and publish sandboxes workflow after merge (or dispatch it against this branch) and confirm react-native-web-vite/expo-ts and react-native-web-vite/rn-cli-ts complete successfully.

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Declare whether manual QA will be needed for this PR during the next release, through qa:needed or qa:skip

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 13 minutes

Limit details: You’ve used all 4 included reviews currently available under your plan. You completed 34 included PR reviews in the past 7 days; at that activity level, included reviews refill at 4 reviews per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5df33ee2-ec03-4a22-ab20-7213a3e3dbbd

📥 Commits

Reviewing files that changed from the base of the PR and between 1578b92 and e2e6585.

📒 Files selected for processing (5)

• .github/workflows/generate-sandboxes.yml
• code/lib/cli-storybook/src/sandbox-templates.ts
• scripts/sandbox/generate.ts
• scripts/sandbox/utils/yarn.test.ts
• scripts/sandbox/utils/yarn.ts

---

_{Comment @coderabbitai help to get the list of available commands.}