CLI: Run storybook dev as part of storybook init

[yannbf]

Closes #22871

What I did

• add --initial-path option to the CLI
• run storybook dev as part of storybook init

How to test

1. Build all packages
2. Create a new project with the CLI e.g. ./code/lib/cli/bin/index.js init --initial-path=/settings/shortcuts
3. Expect Storybook to open in that route

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"]

[yannbf]

Running Storybook automatically. To run it manually, use the following command: xyz

[yannbf]

add it in a box

[yannbf]

@shilman @jonniebigodes here's how it looks like after the change:

For Vite:

For Angular Webpack (the most verbose we have):

Thoughts?

[shilman]

Looks great! I'm sure we can clean all this up if we rework the CLI, but for now I'd say ship it!