Docs: Remove uncessary components

[jonniebigodes]

Closes #

What I did

With this pull request, the documentation was updated to remove some one-off components (i.e., FrameworkSupportTable, FeatureSnippets) to streamline the documentation workflow.

What was done:

• Removed mentioned components.
• Removed the associated MDX-based files
• Polished and restructured the documentation to include the information and conditionally rendered it.
• Created required snippets

@cdedreuille , with this change, we're good to go on removing the components already mentioned and adjusting the components that depend on the frameworks.js as the featureGroups object is no longer in effect the information was converted into a Markdown table.

Checklist for Contributors

Testing

1. Follow the steps in the contributing instructions for this branch, docs_remove_feature_snippet.
2. Open the relevant documentation and verify the feature changes.

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>

[cdedreuille]

That's great @jonniebigodes. If we remove the component, will it have an impact on previous versions?

[jonniebigodes]

@cdedreuille it probably does with the previous versions of documentation.