Minimize Lifecycle Mapping parsing during discovery

Signed-off-by: Fred Bricon <fbricon@gmail.com>
409732 : Split lifecycle mapping analysis from project import

The Lifecycle Mapping analysis is now only run after projects are
imported, making selection of projects to import much much faster (< 1
sec vs 1-2 min for the wildfly codebase and its 130 projects)

After import, lifecycle mapping error markers are collected on imported
projects and the discovery service is invoked to find proposals fixing
these errors.

Caveats :
- no proposals are shown anymore in case projects import without
errors, making discovery of new/other applicable connectors less obvious.

As part of the refactoring the following notable architectural changes
were performed :
- LM Analysis and Discovery proposals UI are moved to a dedicated Wizard.
- LifecycleMappingConfiguration was deprecated in favor of
  LifecycleMappingDiscoveryRequest
  -Lifecycle Mapping discovery is now based on a collection of
  ILifecycleMappingRequirement

Signed-off-by: Fred Bricon <fbricon@gmail.com>