[Maps] show maps in visualize listing page

[nreese]

Embeddable saved objects expose the ability to "Save to library" and "Unlink from library" where "library" is the visualization application. If an embeddable panel is in the "library", then it shows up in visualize listing page and is a by reference saved object.

How will these actions work for Maps?

1. Change the text for map embeddable actions to "Save to maps" and "Unlink from maps". If a map embeddable panel is in "Maps", then it shows up on maps listing page. Chatted with @ThomThomson about this option and we think it adds even more confusion to an already confusing topic. Now users would have to know if the embeddable is going to Maps application or the Visualize application. What happens when ML swimlanes are considered - yikes.
2. Show maps saved objects in visualize listing page. That way, the copy can stay the same for all panels and users go to a single place to look in the "library"

Below are some screen shots showing existing copy for Lens embeddables

cc @AlonaNadler @ryankeairns

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[AlonaNadler]

Embeddable saved objects expose the ability to "Save to library" and "Unlink from library" where "library" is the visualization application. If an embeddable panel is in the "library", then it shows up in visualize listing page and is a by reference saved object.

If I try to look at it from users' perspective. Users don't know what is embeddable (and what is not embeddable). Visualizations can be optionally added to the Visualization library. If visualization is added to the visualization library it will appear on the visualizations library listing page.

When it comes to Maps, do we want to use maps as by value which means they are part of the dashboard? do we want maps to appear in the visualization library?
Sounds like we do. In this case, we can show the maps in both visualizations library and in maps listing but I think the terminology should remain the same and not go into the lines of link/unlik from maps. but rather add to visualization library or when in dashboards unlink from visualization library what do you think?

For ML and in the future observability and security widgets, one option is to add these widgets from a place in the toolbar and called explicitly. I prefer this option because it is more discoverable and highlight the ability to add solutions widgets next to custom visualization

cc: @kmartastic