feat(RadioButton): Improve guidelines to avoid nesting elements (!3809) · Merge requests · GitLab.org / gitlab-services / Pajamas Design System

The MR title and commit messages meet the [Pajamas commit conventions][commits].
The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per [“Say why not just what”][transparency].
- For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
Relevant label(s) are applied to the MR.
The MR is added to a milestone.
If creating a new component page [from scratch][writing-documentation], it follows the [page template structure][page-template].
Content follows the [Pajamas voice and tone guidelines][voice-and-tone], falling back on the [GitLab Documentation Style Guide][style-guide] when needed.
Related pages are cross-linked, where helpful. Component pages have [related components and patterns][related] defined in their Markdown front matter.
If [embedding a Figma file][figma-embed], it follows the [Figma embed guide][figma-embed-guide].
Review requested from any [GitLab designer][design-reviewer] or directly from a [maintainer or trainee maintainer][pajamas-assignments].

feat(RadioButton): Improve guidelines to avoid nesting elements