Track deployment status

[eromanova]

Added a new poller to track the deployments status in the heartbeat event according to the tracking plan every 10 minutes.

Performance testing

To analyse and decrease memory and CPU usage the following approaches were tested on 1000 test deployments:

Testing discovered that the first approach performed best on the management cluster. It was tested using the metrics server (kubectl top pod):

1. List all deployments using the default (cached) manager client

NAMESPACE            NAME                                            CPU           Memory
hmc-system           hmc-controller-manager-58bbbc8d7c-wkpfs         6m            67Mi
kube-system          kube-apiserver-hmc-dev-control-plane            82m           562Mi

2. List all deployments using uncached manager client

NAMESPACE            NAME                                            CPU           Memory
hmc-system           hmc-controller-manager-d8c546f54-667gh          11m           92Mi
kube-system          kube-apiserver-hmc-dev-control-plane            189m          589Mi

3. Use pagination to list limited blocks of deployments with cached client. Rejected since pagination does not work using cached manager client Pagination does not work when using manager client  kubernetes-sigs/controller-runtime#1960

4. Use pagination to list limited blocks of deployments with uncached client

NAMESPACE            NAME                                            CPU           Memory
hmc-system           hmc-controller-manager-6b598b4745-c9tp8         10m           61Mi
kube-system          kube-apiserver-hmc-dev-control-plane            120m          666Mi

Closes #138
Closes #231