LPS-127020 Move autoFocus functionality to the management toolbar taglib

[wincent]

Manual forward from: liferay-frontend#833

CI was green here, other than the known-issue upstream failure (LocalFile.WebContentWithCustomStructures#AddWebContentWithRepeatableRichTextField) that was fixed yesterday.

Original PR description follows.

---

Task ticket: https://issues.liferay.com/browse/LPS-127020
Related discussions:

• Add autoFocus to management toolbar liferay/clay#3895
• [don't forward] LPS-121875 Migrate management toolbar v2 usages in dynamic-data-mapping-web liferay-frontend/liferay-portal#826

Notes:

• By default, we are not auto-focusing the search input. This is because Lexicon does not state this behavior and vast majorities on usages in DXP do not auto-focus. See [don't forward] LPS-121875 Migrate management toolbar v2 usages in dynamic-data-mapping-web liferay-frontend/liferay-portal#826 (comment)
• There is an ongoing discussion about how to name the attribute, see [don't forward] LPS-121875 Migrate management toolbar v2 usages in dynamic-data-mapping-web liferay-frontend/liferay-portal#826 (comment). In this PR I chose searchInputAutoFocus because

<clay:management-toolbar
	searchInputAutoFocus="<%= true %>"
	searchInputName="mySearchInputName"
/>

rhymes with

<ClayInput
	autoFocus={searchInputAutoFocus}
	name={searchInputName}
/>

• Intrestingly, React's autoFocus, capital F, is quite different from HTML autofocus. To prevent cross-browser inconsistencies, they are using a polyfill to call .focus().

/cc @wincent @4lejandrito @jbalsas @julien @jonmak08 @ambrinchaudhary

Test sample in clay-sample-web:

[liferay-continuous-integration]

Closing pull request because all liferay-portal pullrequests sent to Brian Chan must be sent by using ci:forward on a pull request that was sent to someone else.

[wincent]

ci:reopen

[brianchandotcom]

Merged. Thank you.
View total diff: 59ee92b...a35eb22