Update Select for SLDS2

[msmx-mnakagawa]

What I did

• pass id as controlId
• insert .slds-select_container inside the FormElement

Reference

https://v1.lightningdesignsystem.com/components/select/

[reg-suit]

reg-suit detected visual differences.

Check this report, and review them.

🔴🔴🔴🔴🔴🔴🔴🔴

🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵🔵

What do the circles mean?

The number of circles represent the number of changed images.
🔴 : Changed items, ⚪ : New items, ⚫ : Deleted items, and 🔵 Passed items

How can I change the check status?

If reviewers approve this PR, the reg context status will be green automatically.

[Copilot]

Pull Request Overview

This PR updates the Select component to align with SLDS2 guidelines by passing id as htmlFor and inserting the .slds-select_container wrapper for single-select elements.

• Switched FormElement prop from id to htmlFor
• Wrapped non-multiple <select> in a <div className='slds-select_container'>

Comments suppressed due to low confidence (1)

src/scripts/Select.tsx:81

• Consider adding or updating unit tests to cover both rendering paths (with .slds-select_container for single-select and the direct <select> for multiple).

<div className='slds-select_container'>{selectElem}</div>

[Copilot]

[nitpick] Destructuring multiple from props (e.g., const { multiple } = props) and using it directly can improve readability instead of rprops.multiple.

Suggested change

	{rprops.multiple ? (
	{multiple ? (