Vite: Add react docgen types

[IanVS]

Closes #20789

What I did

Adds types for react docgen options to the react-vite framework

How to test

Generate a sandbox for react-vite/default-ts, add an option in the main.ts like:

typescript: {
	reactDocgen: false
}

it should not error.

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

[shilman]

Thanks @IanVS ! Was in the process of submitting my own PR for this but you beat me to it

[shilman]

Should this be Parameters<typeof docgenTypescript>[0]? I think parameters returns an array

[kasperpeulen]

Nice!

[D1no]

@shilman Since you guys seem to work on this, updated the following ticket reproduction to storybook@7.0.0-beta.62

#21399 [Bug]: No JSDoc generation when story outside root or symlinked (MonoRepo Blocker) ts + vite + storybook@7.0.0-beta.62

https://github.com/D1no/reproduction-storybook-symlinks-pnpm

The same component is included as (1) local copy inside stories/, (2) as reference in .storybook/main.ts and as a (3) symbolic link into stories/.

✅ All three types render successfully in storybook.

❌ Only variant (1) has JSDoc converted to story docs (!)

Exact same component and story, but as you see = different location = no JSDocGen.

[IanVS]

@D1no that seems unrelated to this PR. Maybe you're thinking of something else?

[D1no]

@IanVS Maybe. The work on vite typescript docgen seems to be pretty fragmented. Have no insights 🤷🏻‍♂️ overview. If unrelated, ignore.