SelectPanel: Update SelectPanel to use modern ActionList

[broccolinisoup]

Closes #

Changelog

New

Changed

Removed

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7b3d5e6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	94.17 KB (-2.11% 🔽)
packages/react/dist/browser.umd.js	94.56 KB (-1.97% 🔽)

[camertron]

Awesome, nice work! As far as groups go, it looks like both the beta and deprecated versions of ActionList support them. Maybe we could create a sub-component called MappedActionListGroup? Then we could do something like:

function MappedActionListGroup({ items, header }: GroupProps) {
  return (
    <ActionList.Group>
      <ActionList.GroupHeading variant={header.variant}>
        {header.title}
      </ActionList.GroupHeading>
      {items.map((item) => <MappedActionList item={item}>)}
    </ActionList.Group>
  )
}

[camertron]

I'm not sure if this is a common pattern, but I personally find it a bit confusing to use TitleCase for these renamed variables. Can we avoid renaming them, or name them something else, eg. originalTrailingVisual?

[primer-integration]

👋 Hi from github/github! Your integration PR is ready: https://github.com/github/github/pull/337077