Improve API documentation for input components

[jattasNI]

Pull Request

🤨 Rationale

Ongoing efforts towards #824. This PR covers input components:

• select
• combobox
• radio group
• text area
• text field
• number field
• checkbox
• switch

👩‍💻 Implementation

Generally follow patterns from previous PRs like #2126 and #2117. A few interesting notes:

1. components have different behaviors regarding whether they sync their value property to an attribute. I documented the behavior I observed by adding a new table category for properties that don't have attributes (also used by checkbox indeterminate property).
2. not yet documenting a recommendation to use form association / CVAs instead of change events and value properties. Until I do so, the placeholder docs for select are outside any table category.
3. added another new table category for localizable strings.
4. not yet documenting list option API in the select and combobox stories. We (probably Meyer) are going to tackle this in a follow up after #2111.

🧪 Testing

✅ Checklist

• [x] I have updated the project documentation to reflect my changes or determined no changes are needed.

[jattasNI]

@m-akinc would you mind being my buddy for API docs changes while Milan is out of office?

[jattasNI]

Bypassed @rajsite due to OOO.