Automattic Components: Add select dropdown to package

[jeyip]

• Dependent on Automattic Components: Add count to package #79257 and Automattic Components: Add form label to package #79256
• Tracking issue https://github.com/Automattic/martech/issues/2023

Proposed Changes

I understand that these seem like a large volume of changes, but we're simply cloning the existing client/components/ select dropdown component into @automattic/components as we did in #79257 and #79256

The entirety of the migration is a 4 step process that creates easily digestible ( and revertible ) PRs to work with. See https://github.com/Automattic/martech/issues/2028. Unfortunately, this process also eliminates the git history from migrated files unless the 4 steps are condensed into a single one. I don't have a great answer to this, but the tradeoff, to me, is worth the added safety of more understandable, compact, iterative pull requests.

GIFs

Testing Instructions

• Make sure all tests pass. yarn run test-packages packages/components/src/select-dropdown/test if you'd like to run it locally, but the CI process should catch anything.
• At the root of the Calypso directory, run yarn storybook:start
• Ensure that the select-dropdown component renders properly

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-77483

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-77483&env=jetpack

[matticbot]

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

[ddc22]

Had a minor concern but I don't think there is an easy way to resolve it other than doing everything in one go.

Works well, LGTM 🚢

[ddc22]

The only contention I have with this issue is that we loose the blame history of the file once we delete that.

[jeyip]

Ah this is a super interesting point that I also don't have a great answer to. For me, being able to break down the migration into easily digestible PRs is worth the trade off, especially for such a wide reaching component.

At the very least though, I'll go back and make a note in the pull request descriptions for this PR, #79256, and #79257. That way, if anyone else follows this same process, they'll be aware of the tradeoffs from the get-go. If you think of any other suggestions, feel free to let me know and we can try and implement them 👍