Cluster Logging Operator does not start successfully when Elasticsearch operator is not available.

Issue

• Cluster Logging operator constantly keeps restarting right after installation.
• The logs of Cluster Logging operator pods log the following messages:

{"_ts":"2022-12-15T08:58:04.13076532Z","_level":"0","_component":"cluster-logging-operator","_message":"Manager exited non-zero","_error":{"msg":"failed to wait for clusterlogging caches to sync: timed out waiting for cache to be synced"}}

• This issue is observed when Elasticsearch operator is not installed and CRDs of Elasticsearch are not present.