Fixes double deployment for git components on second push and later

[mik-dass]

fixes #1981

How to test:

1. Trigger test-cmd-url on a 4.2 cluster close to 10 times and check if the error described in the issue occurs or not and also if the second push only triggers a single deployment revision.

[mik-dass]

@amitkrout Let's make sure we run this 10+ times on 4.2 cluster before moving forward

[mik-dass]

Unexpected error:
        <*os.PathError | 0xc00008ae40>: {Op: "chdir", Path: "", Err: 0x2}
        chdir : no such file or directory
    occurred

/retest

[mik-dass]

Running odo with args [odo list --project qgxdkrgyyj]
[odo]  ✗  There are no components deployed.

/retest

[mik-dass]

 ✗  Waiting for build to finish [30s]
[odo]  ✗  Failed to create component with name cmp-git. Please use `odo config view` to view settings used to create component. Error: unable to wait for build cmp-git-testing-1 to run: timed out waiting for the condition

/retest

[mik-dass]

level=fatal msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to apply using Terraform"
---
Container test exited with code 1, reason Error
---
Another process exited

/retest

[kadel]

/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kadel

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/occlient/OWNERS [kadel]
• tests/OWNERS [kadel]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[amitkrout]

/retest

[amitkrout]

Will check it on my aws OpenShift 4.2 cluster atleast for 5 consecutive run.
Till then holding the pr
/hold

[amitkrout]

Will check it on my aws OpenShift 4.2 cluster atleast for 5 consecutive run.
Till then holding the pr
/hold

I have executed 5 times on 4.2 OSD real cluster and none of the time i hit the issue of #1981
/hold cancel
/lgtm

[mik-dass]

 ✗  invalid configuration: [context was not found for specified context: zyasqblwkq/api-ci-op-h4d1xz7d-1b2f4-origin-ci-int-aws-dev-rhcloud-com:6443/developer, cluster has no server defined]
[odo] Please login to your server: 

/retest

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.