chore(project): remove unstable prefix for applicable components

[tay1orjones]

Closes #10767

Components that will be moving to "stable" in v11 should be exported from @carbon/react without the unstable prefix

Changelog

Changed

• remove unstable prefix from components that will be stable in v11
• update associated stories to no longer be experimental and include the prefix

Testing / Reviewing

• Did I miss any? Or should something else remain unstable?
• With this PR, we'll continue to have the following unstable components:
  • New Pagination
  • TreeView
  • ContextMenu

[netlify]

✔️ Deploy Preview for carbon-react-next ready!

🔨 Explore the source changes: 2391479

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-react-next/deploys/621e52eed6a6ea0008212b1e

😎 Browse the preview: https://deploy-preview-10768--carbon-react-next.netlify.app

[netlify]

✔️ Deploy Preview for carbon-elements ready!

🔨 Explore the source changes: 2391479

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-elements/deploys/621e52ee3924880007965a5a

😎 Browse the preview: https://deploy-preview-10768--carbon-elements.netlify.app

[netlify]

✔️ Deploy Preview for carbon-components-react ready!
Built without sensitive environment variables

🔨 Explore the source changes: 2391479

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-components-react/deploys/621e52ed427c2c000762e44f

😎 Browse the preview: https://deploy-preview-10768--carbon-components-react.netlify.app

[joshblack]

@tay1orjones I'm not 100% sure about context menu going to stable, is this something that we're tracking in the release? I'm just not aware of it and wanted to check-in

[tay1orjones]

@joshblack Yeah, good question. I mistakenly thought everything delivered in #6830 and the few small follow up fixes we've seen since then put it in a spot of ready to move to stable, but it looks like there's some lingering pieces that need to be addressed.

Notably the wrapping behavior described in #7350 (comment), and some additional issues.

I'll update this PR placing Menu back under unstable.

[janhassel]

@tay1orjones @joshblack Just chiming in. The two outstanding issues (#8073 and #8076) should be addressable without a breaking change. The third one tagged as context menu (#9426) actually requires no work on the Menu component.

I think Menu needs to be promoted to stable with v11 since the OverflowMenu/next implementation is based on it and requires MenuItem to be used instead of OverflowMenuItem. It also adds support for all related components:

• MenuDivider
• MenuGroup
• MenuRadioGroup
• MenuSelectableItem

[dakahn]

looks good to me 👍🏾

[tw15egan]

I think this PR has caused an issue with the V11 storybook https://deploy-preview-10768--carbon-react-next.netlify.app/?path=/story/components-button--default