CLI: Fix storybook dev after storybook init via subprocess

[yannbf]

Closes #

What I did

When executing dev directly in Storybook init, there is a possibility of having the following issue:

WARN   Failed to load preset: "@storybook/react-vite/preset"
ERR! Error: Cannot find module '@storybook/react-vite/preset'
ERR! Require stack:
ERR! - /Users/xyz/.npm/_npx/eb8bf615e50a412a/node_modules/@storybook/core-common/dist/index.js
ERR! - /Users/xyz/.npm/_npx/eb8bf615e50a412a/node_modules/@storybook/telemetry/dist/index.js
ERR! - /Users/xyz/.npm/_npx/eb8bf615e50a412a/node_modules/@storybook/cli/dist/generate.js

This happens because of the location of the packages in node_modules. By spawning a subprocess, this problem goes away as the process executes in the current working directory instead, where the node_modules should be present and correctly resolved.

How to test

1. Build packages and start local registry
2. Set your global registry to: npm config set registry http://localhost:6001
3. Run init e.g. src/lib/cli/bin/index.js init in a react-vite project
4. Things should work

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]