Review plugin containers interface configurations

[allyoucanmap]

Description

At the moment we have plugins container with different interface configurations. A common pattern is to allow to pass a connected react component from the child plugin to the parent container but the naming is inconsistent, eg:

• Map plugin exposes Tool property
• TOC plugin exposes Component property
• SidebarMenu plugin exposes tool property
• BurgerMenu plugin exposes tool property

Following the work done after the introduction of the usePluginItems hooks we could normalize the configuration as follow:

• Component a react component to be used inside the plugin container. Plugin container could pass specific props including an itemComponent prop as a default component for the item (eg. for toolbar or list)
• name identifier for the injected component (optional)
• target a string property supported by the plugin container to render the child item component in a specific section. A plugin container could implement multiple target (optional)

Common configuration already supported

• position (optional)
• priority (optional)
• alwaysRender (optional)
• doNotHide (optional) (to rename?)

{
  PluginContainerName: {
    name: "PluginContainerName",
    Component: ReactComponent,
    target: "menu-left"
  }
}

We could also deprecate previous configuration based on actions (see ToolContainer component) and update everything to the component approach

What kind of improvement you want to add? (check one with "x", remove the others)

• Minor changes to existing features

Other useful information