[bug]: Expo dependencies bypass SDK version resolution

[brilliantinsane]

Describe the bug

When a registry item declares a bare Expo dependency, shadcn should let
expo install choose the version compatible with the project's Expo SDK.

This worked in shadcn@4.13.0, but regressed in 4.13.1.

Using the same registry item in two identical Expo SDK 56 projects:

CLI	Installed @expo/ui	expo install --check
shadcn@4.13.0	~56.0.23	Passes
shadcn@4.13.1	^57.0.7	Fails

The failing project reports:

@expo/ui@57.0.7 - expected version: ~56.0.23
Found outdated dependencies

This was introduced in #11195 when the Expo command changed from:

npx expo install <dependencies>

to:

npx expo install -- <dependencies>

Expo passes arguments after -- directly to the package manager, so those
dependencies skip Expo's SDK version resolution.

A fix is available in #11292. It removes -- only from Expo's normal
dependency path while keeping assertSafeDependencies in place. npm, pnpm,
Yarn, and Bun retain their end-of-options separators.

The PR includes regression coverage for Expo's SDK-aware invocation and verifies
that flag-like dependencies are rejected before starting a process.

Affected component/components

shadcn CLI, Expo dependency installation

How to reproduce

Complete reproduction:

https://github.com/brilliantinsane/shadcn-expo-sdk-resolution-repro/tree/6ca2bece27dea2ecbe81fadd463148aec0935132

The repository contains one Expo SDK 56 template and the completed results from
running the same registry item with shadcn@4.13.0 and shadcn@4.13.1.

The registry input is generic and pinned to a commit:

https://github.com/brilliantinsane/shadcn-expo-registry-fixture/blob/ad2d88d0a3468c6d506fe8d58191ed35cbb7a2da/registry.json

Codesandbox/StackBlitz link

https://github.com/brilliantinsane/shadcn-expo-sdk-resolution-repro/tree/6ca2bece27dea2ecbe81fadd463148aec0935132

System Info

Expo: 56.0.17
React Native: 0.85.3
Package manager: pnpm 11.11.0
Unaffected shadcn version: 4.13.0
Affected shadcn version: 4.13.1

Before submitting

• I've made research efforts and searched the documentation
• I've searched for existing issues