Refactor: Split ngx-launcher in multiple components accessible from client app

[ia3andy]

there are 2 different approaches:

1. In it’s simplest form we go back to the model we had before and let ngx-launcher be a set of components / steps and each project can pick the steps that they want.

We will have as output of the ngx-launcher library:

• one or more components for each steps
• one component ngx-launcher that get steps as input and bind them to make a wizard

Goals:

• Make custom steps in clients
• Avoid having unused dependency editor in standalone launcher
• Give control to client app on steps to use (no more if osio/launch..)

2. More complex idea would be to, still use one component, but use a plugin architecture where we can define and load bits dynamically https://github.com/edewit/angular-plugins

[fabric8cd]

🎉 This issue has been resolved in version 3.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀