User shall know the tools available before defining its own services

[orviz]

Currently the user does not know about what tools are natively supported by the Pipeline as a Service until it reaches the step 3 (criteria), but we are requesting the definition of tooling services in step 2. This means that the user has to go to step 3 and if the tool is not listed there, get back to step 2 to define a container that will provide it.

I see two approaches to circumvent this:

1. Switch steps, so 3 becomes 2 and viceversa
2. Merge step 2 in step 3 as a popup menu