Closes N/A

What I did

This PR implements a significant architectural change in Storybook's testing infrastructure by consolidating the interactions testing functionality from the standalone @storybook/addon-interactions into the core component testing module. This change aims to streamline the testing experience and reduce fragmentation in the codebase.
Key Changes

1. Addon Consolidation

• Removed the standalone @storybook/addon-interactions package
• Moved all interactions-related components and functionality to core/component-testing
• Updated imports and references across the codebase to reflect the new structure

2. Component Migration

The following components were moved from addons/interactions to core/component-testing:

• Interaction.tsx
• InteractionsPanel.tsx
• List.tsx
• MatcherResult.tsx
• MethodCall.tsx
• Panel.tsx
• StatusBadge.tsx
• StatusIcon.tsx
• Subnav.tsx
• TestDiscrepancyMessage.tsx

3. Configuration Updates

• Removed interactions-specific configurations from various project files
• Updated package.json files to remove @storybook/addon-interactions dependencies
• Simplified Storybook configuration files by removing interactions-specific settings
• Updated build and test configurations to reflect the new structure

4. Dependencies Removed from @storybook/addon-test

• @storybook/addon-interactions
• formik
• @devtools-ds/object-inspector
• ansi-to-html
• strip-ansi

Notes

• This change is part of a larger effort to streamline Storybook's testing infrastructure
• The consolidation aims to improve maintainability and reduce confusion about which testing approach to use
• Future improvements to the component testing module will be more straightforward with this unified approach

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-storybook/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 pull request has been released as version 0.0.0-pr-30916-sha-e160c7e2. Try it out in a new sandbox by running npx storybook@0.0.0-pr-30916-sha-e160c7e2 sandbox or in an existing project with npx storybook@0.0.0-pr-30916-sha-e160c7e2 upgrade.

Greptile Summary

Here's a concise summary of this significant architectural change to Storybook's testing infrastructure:

This PR consolidates the interactions testing functionality from @storybook/addon-interactions into the core component testing module, streamlining Storybook's testing infrastructure.

Key changes:

• Moved all interactions components and utilities from addon-interactions to core/component-testing
• Removed standalone @storybook/addon-interactions package and its dependencies
• Updated imports across codebase to reference new core module locations
• Added new component-testing manager and preview entries in core configuration
• Removed addon-interactions from all sandbox and test project configurations

The changes appear well-structured and maintain existing functionality while reducing codebase fragmentation. However, careful testing is needed to ensure all interaction testing capabilities work properly after consolidation.