Track separately current vs target version of a service

Today the "version" of a service refers to the "target version" (the one we are trying to deploy on our cluster). But if a deployment is not triggered or it fails, this version is not representing what's actually available on the cluster

We will separate the two versions making it clear the current vs target version of the application