Add Health status condition in the supply chain section of the workload get output

[atmandhol]

Description of problem

Cartographer v0.4.2 has support for Health rules as mentioned in this RFC.

Proposed solution

Add a column Healthy to show the status of the condition Healthy in the Workload status.

All Healthy Scenario

RESOURCE          READY  HEALTHY  TIME
source-provider   True   True     3d23h
deliverable       True   True     3d23h
image-builder     True   True     3d23h
config-provider   True   True     3d23h
app-config        True   True     3d23h
config-writer     True   True     3d23h

Issues
No issues reported.

Build in progress scenario

RESOURCE          READY     HEALTHY     TIME
source-provider   True      True        3d23h
deliverable       True      True        3d23h
image-builder     Unknown   Unknown     3d23h
config-provider   False     Unknown     3d23h
app-config        False     True        3d23h
config-writer     False     Unknown     3d23h

Issues
reason:    MissingValueAtPath
message:   waiting to read value [.status.latestImage] from resource [image.kpack.io/petc-mvn-release] in namespace [default]
health:    petc-mvn-release-build-1 is executing

cc @danfein for design input.

[danfein]

Table looks good.
Could consider color coding status (true=green, false=red) to make the output easier to scan, doesn't necessarily need to be part of this story though.

Issues section idea: concatenating the reason and message into a single line. It would group the related bits together more closely, so if there are multiple reason:message strings there wouldn't be confusion about which goes with which.

MissingValueAtPath   : waiting to read value [.status.latestImage] from resource [image.kpack.io/petc-mvn-release] ...
HealthyConditionRule : petc-mvn-release-build-1 is executing

The other thought I had was that if more than one resource has an error message, there may be a risk of confusion about which issue maps to which cartographer resource. If we see folks running into that situaton we may need to take another pass to clarify where issues are coming from.

If there is usually a single error, there would not be any confusion.