feat(Select): Add guidelines for select

What does this MR do?

Adds a guideline for when not to use select in a form based on a recent question in Slack.

Is there guidance on when to use a select over radio buttons ? I was planning on moving any select that only has 2 options to radio buttons, but beyond that I'm not sure. In this example, the wiki had 3 options as radio buttons, and the next two select components also have 3 options each - https://gitlab.slack.com/archives/CLW71KM96/p1689870377915889

Does this MR meet the acceptance criteria?

• The MR title and commit messages meet the Pajamas commit conventions.
• 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”.
  • 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, it follows the page template structure.
• Content follows the Pajamas voice and tone guidelines, falling back on the GitLab Documentation Style Guide when needed.
• Related pages are cross-linked, where helpful. Component pages have related components and patterns defined in their Markdown front matter.
• If embedding a Figma file, it follows the Figma embed guide.
• Review requested from any GitLab designer or directly from a maintainer or trainee maintainer.

Links