DataForm: implement toggleGroup Edit control

[fushar]

Related to #103426 (comment)

Proposed Changes

This PR introduces a new Edit control, toggleGroup, to DataForm fields.

Testing Instructions

1. Run yarn workspace @automattic/dataviews storybook:start
2. Verify you can play around with the Status field which uses the new toggleGroup control.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-144588

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-144588&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-144588&env=a8c-for-agencies

[fushar]

This file is almost a verbatim copy of the existing radio control, with some modifications.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~79 bytes added 📈 [gzipped])

name                parsed_size           gzip_size
staging-site             +636 B  (+0.0%)      +79 B  (+0.0%)
sites-dashboard          +636 B  (+0.1%)      +79 B  (+0.0%)
site-settings            +636 B  (+0.0%)      +79 B  (+0.0%)
site-performance         +636 B  (+0.0%)      +79 B  (+0.0%)
site-monitoring          +636 B  (+0.1%)      +79 B  (+0.0%)
site-logs                +636 B  (+0.1%)      +79 B  (+0.0%)
plans                    +636 B  (+0.0%)      +79 B  (+0.0%)
overview                 +636 B  (+0.0%)      +79 B  (+0.0%)
hosting                  +636 B  (+0.0%)      +79 B  (+0.0%)
github-deployments       +636 B  (+0.1%)      +79 B  (+0.0%)
domains                  +636 B  (+0.0%)      +79 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• help-center
• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug dataform-toggle-group on your sandbox.

[arthur791004]

👍

[oandregal]

This is great, thank you. I left a comment about camelCase vs kebab-case, and I think we should prefer the former unless there's any specific reason for the choice.

This works well, and it's ready to land in my view. Just for awareness, when working with DataForm we need to test a few configurations: type of form (regular or panel) and label position (top, side, none):

Screen.Recording.2025-05-16.at.10.52.41.mov

[fushar]

Just for awareness, when working with DataForm we need to test a few configurations: type of form (regular or panel) and label position (top, side, none):

Yup, I did. 😄

[oandregal]

Yup, I did. 😄

Nice, thank you. I wasn't aware if you were aware, so I thought it'd be best to over-communicate just in case. :)