chore(FilteredActionList): fix className override

[francinelucca]

Component prop handling improvements:

• In FilteredActionList.tsx, destructured className from textInputProps and renamed the remainder to restTextInputProps for clearer prop management.
• Updated the TextInput element to use the separated textInputClassName and conditionally apply the FullScreenTextInput class, while spreading only the remaining props. This prevents className from being overridden and ensures correct class application.

[changeset-bot]

🦋 Changeset detected

Latest commit: 04c0627

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@primer/react	Patch
@primer/styled-react	Patch

Not sure what this means? Click here to learn what changesets are.

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

[Copilot]

Pull Request Overview

This PR fixes prop handling in the FilteredActionList component to prevent className overrides. The change ensures that the className prop from textInputProps is properly separated and combined with conditional classes, rather than being overridden by the spread operator.

• Destructures className from textInputProps for explicit handling
• Updates the TextInput element to use the separated className and apply conditional styling correctly
• Prevents className override by moving the spread operator after the className prop

[Copilot]

[nitpick] The conditional object syntax {[classes.FullScreenTextInput]: fullScreenOnNarrow} is less readable than the previous fullScreenOnNarrow && classes.FullScreenTextInput pattern. Consider reverting to the more explicit conditional for better readability.

Suggested change

	className={clsx(textInputClassName, {[classes.FullScreenTextInput]: fullScreenOnNarrow})}
	className={clsx(textInputClassName, fullScreenOnNarrow && classes.FullScreenTextInput)}

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks!