eliminate double bc reporting in status

[deads2k]

Fixes #5360

New output looks like:

[deads@deads-dev-01 origin]$ oc new-project one
[deads@deads-dev-01 origin]$ oc new-build openshift/nodejs-010-
[deads@deads-dev-01 origin]$ oc status
In project one on server https://localhost:8443

bc/nodejs-ex builds https://github.com/openshift/nodejs-ex.git with one/nodejs-010-centos7:latest
  #1 build new for 1 seconds (can't push to image)

[deads@deads-dev-01 origin]$ oc new-project two
[deads@deads-dev-01 origin]$ oc new-app https://github.com/openshift/ruby-hello-world
[deads@deads-dev-01 origin]$ oc status
In project two on server https://localhost:8443

svc/ruby-hello-world - 172.30.126.54:8080
  dc/ruby-hello-world deploys imagestreamtag/ruby-hello-world:latest <-
    bc/ruby-hello-world docker build of https://github.com/openshift/ruby-hello-world 
      #1 build new for 1 seconds (can't push to image)
    #1 deployment waiting on image or update

@Kargakis ptal

[0xmichalis]

LGTM

[deads2k]

[test]

[deads2k]

UI flake #5854

re[test]

[openshift-bot]

Evaluated for origin test up to d53ff13

[openshift-bot]

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/7057/)

[liggitt]

[merge]

[openshift-bot]

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/3995/) (Image: devenv-rhel7_2700)

[openshift-bot]

Evaluated for origin merge up to d53ff13