Orphan ClusterFlow and ClusterOutput resources are not reflected in their status

[pepov]

The status of the ClusterFlow and ClusterOutput resources should highlight when they are not in the configured controlNamespace.

Solution idea:
collect all the ClusterFlows and ClusterOutputs with other logging resources that are not matching with the control namespace as well and then go through them in the validationreconiler to update their status.

[pepov]

All flow and output resources should have their managing logging resource's name in their status, so that we can easily identify those resources that are orphan.

[csatib02]

This was partially solved in: #1825

[csatib02]

This issue was created a long time ago. Ever since then, the validation reconciler was introduced, so this issue was resolved.

Currently, if a flow/clusterFlow or output/clusterOutput has a completely empty Status field, it is considered orphaned, since if it would have been selected by a logging resource, the status fields would be filled out promptly.