Description

Following the issue opened here #9367

This issue will contain discussion and relevant info related to the abstraction level required to plug more easily new processes for the future, this includes

• avoid to run a describe process for all processes and do a selective check instead based on current selection of the tool to be used
• create a Feature Selector component that can manage click and feature info on map, that can be isolated
• review if other logic needs this level of abstraction, in particular when
  • running a process
  • fetching info for the ui
• add a generic file that can list possible processes that will be included in the combobox to be selected
  • this can include a RunComponent
  • a function to know when the run component must be disabled based on some props
  • a Confirm modal if any used to popup when pressing enter
• (optional) possibility to configure which files can be used trough a plugin Cfg

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

• Minor changes to existing features
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

Other useful information

relevant parts for the feature selector