Documentation: Document @storybook/test package

[yannbf]

Relates to #23871

What I did

This PR proposes changes to the documentation in Storybook 8, following the requirements of #23871, to:

• use @storybook/test instead of @storybook/testing-library and @storybook/jest in every setup docs
• use @storybook/test instead of @storybook/testing-library and @storybook/jest in every code snippet
• de-emphasize argTypesRegex
• revamp Addon-actions docs to mention about the explicit fn functions and its connection to actions panel

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]

Noting for posterity:

Once this PR is merged, two things need to happen, in this order (ping me to do it):

1. Configure frontpage's Netlify to build the release-8-0 branch
2. Merge Hide v8 from VersionSelector menu frontpage#603

[ndelangen]

@kasperpeulen @yannbf Is this ready?

[yannbf]

Like we discussed yesterday, there might be the need of writing a migration note, and checking whether the new package clashes with the other packages (sb/testing-lib, sb/jest)

@kasperpeulen can you do that?

[kasperpeulen]

@kylegach I would like to merge this PR and get it in the docs, if you are okay with that :)

@yannbf I found that the packages don't clash anymore, and can be used together in stories, when migrating.
Shall we make the migration note part of this PR?

I think it would be good already start documenting the test package also in the README of the package as @IanVS suggested.

[kasperpeulen]

LGTM!

[yannbf]

@yannbf I found that the packages don't clash anymore, and can be used together in stories, when migrating. Shall we make the migration note part of this PR?

I think it would be good already start documenting the test package also in the README of the package as @IanVS suggested.

Yes please, feel free to do that!