Misconfiguration of a single FTC prevents the FTC controller from progressing

[limhawjia]

Because certain controllers (e.g. status aggregation controller) run by the FTC controller wait for cache sync in the main thread, a wrongly configured FTC can prevent the whole FTC controller from progressing.

The image above shows the logs from the FTC controller indicating that it got blocked after starting the status controller.

Steps to reproduce:

1. Run the KubeAdmiral controller manager against a 1.23 Kubernetes host cluster using the default FTCs in config/sample/host/01-ftc.yaml.
2. Because the yaml file contains an older version of CronJob, informers for CronJob will fail to list and their informer cache will never be synced, resulting in the above behavior

[gary-lgy]

Is this issue still relevant now that we have switched to InformerManager to manage the informers? @limhawjia