Docs: Fix ArgTypes links

[jonniebigodes]

Addresses #22970

What I did

With this pull request, the ArgTypes links were updated to prevent them from 404ing in the documentation, whether viewing the source or, for instance, the pre-release version available. Originally reported here.

A simple test to verify this is to open the Vite builder pre-release documentation and click the link pointing to the ArgTypes documentation which will cause the 404. This can also be replicated by viewing the documentation in situ here on GitHub.

@kylegach I saw that you have a redirect in place, which helped out when the changes came online, but now is having a negative impact as the previous versions of the documentation are also 404ing (e.g., version 7.5, 7.4, etc). Can we mitigate this and set up something for those versions?

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>

[kylegach]

@kylegach I saw that you have a redirect in place, which helped out when the changes came online, but now is having a negative impact as the previous versions of the documentation are also 404ing (e.g., version 7.5, 7.4, etc). Can we mitigate this and set up something for those versions?

Thanks for letting me know. This should be addressed in storybookjs/frontpage#641

[kylegach]

Thanks for taking care of this!