Upgrades verification

[prabalsharma]

To verify upgrades are working as intended:

when I run make kubecf-upgrade,

1. display deployed version of kubecf (helm list --all-namespaces would suffice)
2. create pre-upgrade org, space and user (https://github.com/SUSE/cf-ci/blob/develop/qa-pipelines/tasks/cf-upgrade.sh#L29-L36)
3. deploy an app with instance count equal to diego cells if deployment is using diego (https://github.com/SUSE/cf-ci/blob/develop/qa-pipelines/tasks/cf-upgrade.sh#L37-L42)
4. start a background process to check downtime of the deployed app (https://github.com/SUSE/cf-ci/blob/develop/qa-pipelines/tasks/cf-upgrade.sh#L44-L45)
5. initiate upgrades
6. check if upgrades are successful (already implemented)
7. display deployed version of kubecf (helm list --all-namespaces would suffice)
8. list all orgs and users (https://github.com/SUSE/cf-ci/blob/develop/qa-pipelines/tasks/cf-upgrade.sh#L97-L103)
9. if there is an app downtime, wait for it to be up (https://github.com/SUSE/cf-ci/blob/develop/qa-pipelines/tasks/cf-upgrade.sh#L105-L108)
10. once the app is up and running post-upgrades, kill the app monitoring background process (https://github.com/SUSE/cf-ci/blob/develop/qa-pipelines/tasks/cf-upgrade.sh#L110-L115)
11. display results of app downtime monitoring log (https://github.com/SUSE/cf-ci/blob/develop/qa-pipelines/tasks/cf-upgrade.sh#L117-L119)
12. cleanup created org and deployed app (https://github.com/SUSE/cf-ci/blob/develop/qa-pipelines/tasks/cf-upgrade.sh#L120-L122)