Requested altinity-dashboard features for operators

[hodgesrm]

This issue summarizes feature requests on operators for the Altinity Dashboard. The goal is to make operators easier to understand.

The current UI shows a list of operators in the ClickHouse Operators tab. For each of the operators listed it should be possible to perform the following operations.

1. Show the operator components and their health. (clickhouse-operator and metrics-exporter).

2. Tail logs of each component, equivalent to the following command: kubectl logs -f -n kube-system pod/clickhouse-operator-6fd75cbd68-gw5sg clickhouse-operator (tails one of the operator components)

3. Remove, upgrade, or restart the operator.

[hodgesrm]

One more feature. It would be incredibly helpful if it were possible to show just errors in the operator log, so you could quickly figure out why a ClickHouse cluster is not working.

[alex-zaitsev]

Unfortunately you can not see it from the operator log. Usually need to check statefulset or pod events.

[ghjm]

I believe everything in this issue is complete, except for tailing the logs, which I think is post-MVP. I have opened #59 to track that feature. Closing this issue. (Reopen or submit a new issue if you think I've missed something.)