Finesse health reports, actually print the table not its string.

[fasaxc]

Description

Noticed that the nicely formatted table of health reports was being printed as a JSON-encoded string, making it completely unreadable. Fix that up along with another small niggle; the health report changed log was printing confusing output that made it look like a readiness-only health report was non-live.

New output:

2022-10-11 14:24:42.376 [INFO][98] felix/health.go 263: Overall health status changed: live=true ready=true
+---------------------------+---------+----------------+-----------------+--------+
|         COMPONENT         | TIMEOUT |    LIVENESS    |    READINESS    | DETAIL |
+---------------------------+---------+----------------+-----------------+--------+
| async_calc_graph          | 20s     | reporting live | reporting ready |        |
| egress-networking-in-sync | 0s      | -              | reporting ready |        |
| felix-startup             | 0s      | reporting live | reporting ready |        |
| int_dataplane             | 1m30s   | reporting live | reporting ready |        |
| l7_reporter               | 20s     | reporting live | reporting ready |        |
+---------------------------+---------+----------------+-----------------+--------+

Related issues/PRs

Todos

• Tests
• Documentation
• Release note

Release Note

Improve formatting of logged-out health reports from components such as Felix.

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

• docs-pr-required: This change requires a change to the documentation that has not been completed yet.
• docs-completed: This change has all necessary documentation completed.
• docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

• release-note-required: This PR has user-facing changes. Most PRs should have this label.
• release-note-not-required: This PR has no user-facing changes.

Other optional labels:

• cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
• needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.