Document SearchBar changes from Security migration

[elycheea]

(See example)

Review original SearchBar component from v1 IBM Products / Security against the new version introduced in main.
Update migration notes in Box.

[elycheea]

Prop updates

This is as implemented in initial PR. Props still subject to change during subsequent reviews, especially around the time of release review.

e.g. placeHolderText may become placeholderText.

Old prop	New prop	Change
className	className	—
clearButtonLabelText	clearButtonLabelText	—
hideScopesLabel	hideScopesLabel	—
labelText	labelText	No longer required
onChange	onChange	—
onSubmit	onSubmit	—
placeHolderText	placeHolderText	— Suggest changing to placeholderText
scopeToString	scopeToString	—
scopes	scopes	—
scopesTypeLabel	scopesTypeLabel	—
selectedScopes	selectedScopes	—
sortItems	sortItems	—
submitLabel	submitLabel	—
titleText	titleText	—
translateWithId	translateWithId	—
value	value	—

Additional notes —

• FYI, noticing that several of the props, (scopesTypeLabel, scopes, selectedScopes, translateWithId, sortItems) are meant to be passed to the MultiSelect. Since these are all related, I wonder if it would make sense to follow the approach from @davidmenendez where we have Dropdown in AddSelect and we group these related props in an object/array.
• Don’t think we see titleText in use at all so may be worth deprecating. Actually, it looks like another MultiSelect prop only don’t see it passed anywhere. May be okay to remove if we use the approach from David? 🤔
• Should set controls for more search bar props in Storybook.

[davidmenendez]

FYI, noticing that several of the props, (scopesTypeLabel, scopes, selectedScopes, translateWithId, sortItems) are meant to be passed to the MultiSelect. Since these are all related, I wonder if it would make sense to follow the approach from @davidmenendez where we have Dropdown in AddSelect and we group these related props in an object/array.

yeah i agree with this. basically any time that we're working with multiple carbon components we should do our best to enable users to pass as many props to those components for maximum flexibility. unless there's a specific callout in the design to not use something specific we should probably have something like btnProps = {} and multiSelectProps = {}