Vue: Improve types for array, union and intersection when using vue-docgen-api

[larsrickert]

What I did

• add tests for extracting arg types for "vue-docgen-api"
• fix(vue-component-meta): correctly convert union types with complex schema (e.g. MyNestedProps | MyIgnoredNestedProps)
• fix(vue-component-meta): correctly convert union type with primitive types (e.g. string | number)
• removed unused test mock data
• refactor: separate arg extraction for vue-docgen-api and vue-component-meta to have full type support / safety for each plugin
• vue-docgen-api: improve type docs for array, union and intersection types
• vue-docgen-api: add event data types
• vue-docgen-api: add slot bindings/props
• vue-docgen-api: add missing asterisk for required props

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

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

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>

[kasperpeulen]

LGTM