oc status should add events with type warning or error to the status output

[smarterclayton]

Had an RC that was failing to scale up:

Events:
  FirstSeen	LastSeen	Count	From			SubObjectPath	Type		Reason		Message
  ---------	--------	-----	----			-------------	--------	------		-------
  8m		3m		17	replication-controller			Warning		FailedCreate	Error creating: pods "sub-1-" is forbidden: service account periscope/sub was not found, retry after the service account is created

oc status didn't show any relevant info. We should probably add events of type warning or error as warnings or errors in oc status and make them obvious. We should probably also have the DC controller rolling up conditions onto the DC, and then have oc status show the dc conditions.

[smarterclayton]

@openshift/sig-user-interface

[juanvallejo]

cc @deads2k

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[jwforres]

/lifecycle frozen

[jwforres]

/remove-lifecycle stale