Installer PR landed, which means future 4.2 installer builds will no longer contain "dirty". I'm moving this over to 'oc' so they can address their side of this (likely through version injection when extracting tools from the release image). Then we'll hop on and use the same code to get extraction-time version injection in the installer.

(In reply to W. Trevor King from comment #5)
> Installer PR landed, which means future 4.2 installer builds will no longer
> contain "dirty". I'm moving this over to 'oc' so they can address their
> side of this (likely through version injection when extracting tools from
> the release image). Then we'll hop on and use the same code to get
> extraction-time version injection in the installer.
If half of this is fixed we should someone denote this!
We either need to mark this for 4.2 (what I am doing) and fix both parts (preferred)
or isolate this bug to the 'openshift-installer' parts and create an 'oc' bug to track when 'oc' will fix this.

> Could move to VERIFIED once ON_QA
Do we need to track down the oc commit that fixed this? If not, we could just move this back to MODIFIED and the ART sweeper will pull it into ON_QA the next time it runs.

The oc version just go an upgrade to how it prints version, current output is:
$ oc version
Client Version: v4.2.0-alpha.0-58-g71775b7
Server Version: 4.2.0-0.ci-2019-09-05-164031
Kubernetes Version: v1.14.0+56982c1
which is oc from latest payload. It's clean and simple, dirty I'm assuming is coming from ART and we should not quite worry
about it. We will work with art to figure this out in the next release, for now I'm lowering the priority and pushing this
to 4.3.