Description of problem:
Manually deploy a dc, its trigger cause is shown as same as the previous one. i.e., if previous one is caused by config/image change, the new one is also shown as config/image change. The new one should be shown as manual deployed thus it won't give a misleading feel.

Compared with build, for a build from image/config change, its cause is shown image/config change; while for a build from "oc start-build bc", the new build is shown as manual build both in CLI and web console which therefore does not give a misleading feel.

Version-Release number of selected component (if applicable):
OCP v3.3.0.27

How reproducible:
Always

Steps to Reproduce:
1. Create a dc
1> $ oc new-app openshift/hello-openshift --name hello
2> After hello-1 is deployed, check its trigger cause:
$ oc get dc hello -o yaml
...
      type: ImageChange
    message: caused by an image change
  latestVersion: 1
...

2. Given #1 trigger cause is image change, manually deploy and check trigger cause
1> $ oc deploy hello --latest
2> $ oc get dc hello -o yaml
...
      type: ImageChange
    message: caused by an image change
  latestVersion: 2
...

3. Trigger a config change deployment and check trigger cause
1> $ oc set env dc hello MY_ENV=123
2> $ oc get dc hello -o yaml
...
    - type: ConfigChange
    message: caused by a config change
  latestVersion: 3
...

4. Given #3 trigger cause is config change, manually deploy and check trigger cause
1> $ oc deploy hello --latest
2> $ oc get dc hello -o yaml
...
      type: ImageChange
    message: caused by a config change
  latestVersion: 4
...

Actual results:
hello-2 and hello-4 are shown same trigger cause as previous one. This is also shown on web console deployment page, see attachment, which is somewhat misleading.

Expected results:
hello-2 and hello-4 should be shown manually deployed as trigger cause

Additional info: