Add script to append appropriate package version tags in snippets

[kylegach]

Warning

This PR contains a commit to update docs-versions for QA purposes that must be removed prior to merging.

Before

npx storybook init

After (latest)

npx storybook@latest init

After (pre-release)

npx storybook@next init

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 19, 2024 3:55pm
web-addon-catalog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 19, 2024 3:55pm

[kylegach]

@jonniebigodes — Could you QA this please?

Here's example links:

Latest:

• /docs
• /docs/configure/upgrading

Pre-release:

Temporarily enabled, just to QA this PR

• /docs/8.3
• /docs/8.3/configure/upgrading

If you're curious, you can see which pages & snippets I explicitly disallow from manipulation here:
https://github.com/storybookjs/web/blob/kylegach/sb-1283-docs-issue-with-prereleases-and-snippet-package-labels/apps/frontpage/scripts/append-package-tags-in-snippets.ts#L10-L17

[jonniebigodes]

@kylegach will do. So far I noticed that the builders/webpack page includes the next tag in both @storybook/addon-webpack5-compiler-babel and @storybook/addon-webpack5-compiler-swc addons, despite it being on the disallowed list here. And this has a compound effect on other pages as well where the snippet is used, namely in some of the framework pages (e.g., React & Webpack, addon migration guide)

[jonniebigodes]

Following up on the QA process, I've also noticed that in the Addons/Install page, specifically here the addon snippet is incorrect.
What should be shown would be npx | pnpm dlx | yarn dlx storybook@next add @storybook/addon-a11y as already documented in the remove section.
The upgrade documentation references next, while the rest of the documentation refers to latest. A similar situation is happening in the migration guide where we're referencing latest in a code example that is being documented on a pre-release version and this should not be the case as it will introduce a misconception.