CLI: Fix Javascript language detection

[valentinpalkovic]

Closes #23390

What I did

Fixed language detection to circumvent detecting Typescript, although t isn't a direct dependency

How to test

1. npx create-react-app my-app
2. Initialize Storybook on top of it
3. Javascript stories should be generated instead of Typescript ones.

-->

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]

This change could cause the opposite effect on projects that are typescript but do not have typescript as a dependency/peerDependency, or where typescript comes from a "utility package" e.g. @my-company/developer-tools. I'm also not sure how this would behave in a monorepo that has a single package.json at the root.

Generally LGTM but I'd suggest trying this out in a monorepo setting

[valentinpalkovic]

@yannbf I think your concerns are valid, but the PR now more or less reverts the logic, which was introduced recently, and now the detection should behave the same way as in 7.0.x. I honestly do not know how to fix this issue in mono repo setups since the loaded package.json may vary. Should we possibly introduce a flag to make it possible to manually set the language for these cases?

[valentinpalkovic]

We could also prompt a question if we find typescript somewhere in the node_modules, but not in the package.json, which is known to Storybook. This solution would be the cleanest.