React|WC Parity: Sync existing components

[kennylam]

Update existing web components to match React. Experimental components/features can be excluded until they reach stable status in React. Tests (unit, avt/vrt) can be skipped for now. This is debt we will have to accept, since the testing suite will be getting an overhaul.

Acceptance Criteria for each issue

• update API for new/deprecated functionality
  • in cases where this can cause breaking changes (like changing a property name), the old property name should be @deprecated in addition to adding a new one
• update component visuals/styles
• Storybook stories and documentation (match React story docs wherever possible)

For reviewers of the PRs

• Check against the four themes
• Check against the different browsers
• Storybooks need to match
  • Controls - i.e. RTL - visually make they present. Also make sure they work!
  • Ensure the prop tables have parity.

New Bugs

What should design do if we see a bug in React, do we fix it now in this PR or do we open a separate?

• open a separate issue!

Differences between React and WC

Devs make sure to note where there are WC specific storybook experiences that won't be present in React.

Accessibility

• Do we have Ragu review the Deploy Preview if there are accessibility concerns?
  • How likely is it that his feedback would require a breaking change?
  • Suggest that he's a non-blocking portion of the review. Raise an issue for him to review.

Important

Every PR needs a ux and visual review from the design team to ensure consistency. Please be sure PRs have status: visual review 🔍 applied and request a review from @carbon-design-system/design

existing web components

• Ai-label
• Aspect-ratio
• Code-snippet
• Content-switcher
• Data-table
• Date-picker
• File-uploader
• Form-group
• Icon-button
• Modal
• Notifications #18877
• Number-input
• Pagination
• Popover
• Progress-bar
• Progress-indicator
• Radio-button
• Structured-list
• Tabs
• Text-area
• Text-input
• Toggle
• Toggle-tip
• Tooltip
• UiShell