feat: Added vue docgen options for vite builds

[OssamaSijbesma]

Closes #22909

What I did

I added the possibility to configure the vue docgen options for advanced usage in Vite. For example for monorepo file aliases for docs.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

1. Added logging to the preset.ts and vue-docgen.ts.
2. Run a sandbox for template, e.g. yarn task --task sandbox --start-from auto --template vue3-vite/default-ts.
3. Change the main.ts options (repeatedly based on those options: https://vue-styleguidist.github.io/docs/Docgen.html#api)
4. Checked if the variables are passed correctly and output.

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

[JReinhold]

Thanks for this! We're thinking about migration Vue docgen to Volar, how does this relate to that? Is this related/compatible with that, or is this different?

[kasperpeulen]

cc @chakAs3

[chakAs3]

Yes there is already a PR opened addressing docgen, as @JReinhold said we moving to the official Vue language tools.
@kasperpeulen i will be checking the performance issue on the code transform, so we can merge it next week.

[chakAs3]

Hi @OssamaSijbesma I'm suggestion to open an other PR after merging #22285, please check it out and see if you think the PR still relevant, so we can workout the merge

[ndelangen]

Does this do the same as this PR: #22153

Or should we continue to have both?
WDYT @chakAs3 @OssamaSijbesma @JReinhold ?

[ndelangen]

Please re-open if indeed relevant.