In order to achieve the ticket beahviour we have the following options:

1. extend the step lifecycle to include a verification stage to be executed after the step and outputs are created.
2. to leverage helm release wait lifecycle: to use existing flux verify logic to do the heavy lifting for us
3. to create verification steps - verify wge step.
4. to embed within the step business logic

Preferred options:

1. option 2: helm release: because does not require custom implementation
   // limitation: is it feasible to achieve it with helm release with dependencies
   // scenario: i wait for enterprise helm release ->
   // - cluster-services deploy ok but cluster-controller fails ... would the helm release wait fail?
2. option 1: extend step lifecycle: because allows custom verification logic and it is common to any step

Verify preferred options with the following two scenarios:

1. if cluster-service is deployed correctly and cluster-xx controller fails (as example of a dependency installed via wge helm chart), then install wge install step fails with error
2. if cluster-service and all controllers deploy successfully, then install wge step does not fail.