[shared-ux] Migrate add from library button to shared ux directory

[rshen91]

Summary

This PR migrates the add from library button from the presentation_utils directory to shared_ux. The primary button has already been migrated in #125998.

• Solution Toolbar Button Props do not need to be exposed/exported now since this is the only instance of the button props being referenced

Checklist

Delete any items that are not applicable to this PR.

• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: b1327da
• Interpreting CI Failures
• Storybooks Preview
• Webpack Bundle Analyzer

Failed CI Steps

• Jest Tests #3
• Checks

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/shared-ux-components	2	4	+2

Unknown metric groups

API count

id	before	after	diff
@kbn/shared-ux-components	18	20	+2

History

• 💚 Build #31106 succeeded c05fb18
• 💔 Build #31073 failed 85ad863
• 💔 Build #31018 failed eb90130
• 💚 Build #30744 succeeded fe14cb2

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[cchaos]

TBH, I don't really understand the utility of this button as a "Shared" component. It's simply an instance of the already existing shared component ToolbarButton. Mainly I'm struggling to understand the strategy while converting these to shared-ux components. I think it's worthwhile to reconsider what exists before just doing a straight conversion.

For example, considering that this new AddFromLibraryButton component is actually a very consistently messaged and opinionated component we want folks to re-use, should that just be the component and not have ToolbarButton at all since all that ToolbarButton does is pass props through to an already known component EuiButton.

This may be discussion that needs to happen with the greater team around conversion strategy.

cc @clintandrewhall @majagrubic

[majagrubic]

Left some comments, mostly nits and some cleanup

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: aca6c48
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
dataViewEditor	130	131	+1

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/shared-ux-components	2	4	+2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
dataViewEditor	140.2KB	140.2KB	+74.0B

Unknown metric groups

API count

id	before	after	diff
@kbn/shared-ux-components	22	24	+2

async chunk count

id	before	after	diff
dataViewEditor	6	5	-1

History

• 💚 Build #32209 succeeded 7aa5853
• 💔 Build #32207 failed 7140323
• 💚 Build #31863 succeeded 19e27a5
• 💚 Build #31814 succeeded b0ce01f
• 💚 Build #31526 succeeded f9361a3
• 💛 Build #31454 was flaky 4111c41

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @rshen91