Blocks: Support subcomponents in ArgTypes and Controls, remove ArgsTable block

[JReinhold]

Closes #20782

What I did

#20782 (comment)

• Ported over subcomponents support to the ArgTypes and Controls doc blocks (this means that autodocs now supports subcomponents natively
• Removed the ArgsTable doc block, as this was the last blocker to remove it
• Removed deprecation warnings about subcomponents

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

1. Run a sandbox for template, e.g. yarn task --task sandbox --start-from auto --template react-vite/default-ts
2. Add a subcomponent to Header.stories.ts:

...
import { Header } from './Header';
import { Button } from './Button';

const meta = {
  title: 'Example/Header',
  component: Header,
  subcomponents: { Button },
  // This component will have an automatically generated Autodocs entry: https://storybook.js.org/docs/writing-docs/autodocs
  tags: ['autodocs'],
  parameters: {
    // More on how to position stories at: https://storybook.js.org/docs/configure/story-layout
    layout: 'fullscreen',
  },
} satisfies Meta<typeof Header>;
...

3. Visit autodocs for Header stories and see the "Button" tab in the controls panel. http://localhost:6006/?path=/docs/example-header--docs

4. Add a new MDX file with the following content:

import * as HeaderStories from './Header.stories';
import { ArgTypes, Controls, Canvas } from '@storybook/blocks';

# ArgTypes

<ArgTypes of={HeaderStories} />

# Controls

<Canvas of={HeaderStories.LoggedIn} />
<Controls of={HeaderStories.LoggedIn} />

5. Open it in Storybook and see the two tables now also have the Button tab.

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>

[shilman]

I didn't review all the stories -- will leave that to @kasperpeulen . I wonder if you want to mark them as { chromatic: { disable: true } } just to save some resources.