Charles is undeploying unused components before confirming that the whole release was deployed succesfully

[lucasbfernandes]

Describe the bug
When deploying a new release, Charles first deploys the Kubernetes pods and then triggers the Virtual Service deployment if ALL previous deployments worked correctly. If any component deployment fails, the Virtual Service deployment is not triggered and therefore the previous state of the cluster should be preserved.

During the first deployment phase, if the new deployment resulted in any unused versions, they are all undeployed immediately, which is not correct, because there is a chance the new deployment will not be used (Explained in the first paragraph).

To Reproduce
Steps to reproduce the behavior:

1. Prepare one cluster with only 3 components deployed
2. Deploy a release with new versions from the same 3 components described in step 1
3. Expect one component deployment to fail
4. See the virtual service pointing to inexistent versions in the cluster

Possible Solution
Move undeployment step to the same pipeline used for deploying the Virtual Service/Destination Rules

[lucasbfernandes]

Created a fix: #228.