fix(admin): use control-generic wording for selectable prop docs [2025-10]

[sordaz00]

Backport of #4667 to 2025-10.

What

Four shared declarations describe themselves as a checkbox, and all of them are inherited by components that aren't checkboxes:

• BaseSelectableProps (disabled, value) → BaseOptionProps → Choice, Option
• BaseCheckableProps (label, name) → Switch
• PreactCheckboxProps / PreactCheckboxElement (value) → Switch (SwitchProps extends PreactCheckboxProps, class Switch extends PreactCheckboxElement)

Wording

"checkbox" → "control". State verbs follow each interface's own family vocabulary: BaseSelectableProps uses selected (matching its name and the Option/Choice wording), the checkable declarations keep checked. "control" matches ui-api-design, the upstream source of truth.

Change

Same 8 sentence-level replacements as #4667, applied to this branch's components.d.ts and generated docs. Each is asserted to appear an exact expected number of times before writing, so version drift fails loudly rather than silently no-op'ing. Generated JSON was patched textually rather than regenerated; all files re-parse as valid JSON and the diff is symmetric (4 files changed, 150 insertions(+), 150 deletions(-)).

Refs shop/issues-learn#2959

🤖 Generated with Claude Code

[github-actions]

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset directory. If the changes are user-facing and should cause a version bump, run yarn changeset to track your changes and include them in the next release CHANGELOG. If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.