Signed-off-by: Andreas Karis <ak.karis@gmail.com>

When the Forwarder is enabled, make sure that
clusterLogging.Spec.Collection is non nil to avoid nil pointer
exceptions from occurring.

Signed-off-by: Andreas Karis <ak.karis@gmail.com>

Replacing the CLF Status field causes the resourceVersion to be updated
constantly due to changing timestamps in Status conditions. This in
turn leads to an infinite reconciliation loop. Instead, synchronize all
status conditions so that timestamps remain unchanged if conditions are
not changed.

Signed-off-by: Andreas Karis <ak.karis@gmail.com>

After a valid ClusterLogForwarder and an invalid ClusterLogging resource
are created, the ClusterLogForwarder's status will show that the CLF is
not available. When the ClusterLogging CR is then changes to a valid
configuration, the CLF's status should reflect that everything is o.k.
now.

Signed-off-by: Andreas Karis <ak.karis@gmail.com>