Bug 1884275

Description of problem:

The ClusterLogForwarder API is in cluster scope, but the ClusterLogging API is in namespace scope in the openshift-logging namespace. This inconsistency is confusing for users and creates potential problems for future implementation work.

Version-Release number of selected component (if applicable):

Unreleased as yet.

Futher details:

There's no good reason to cluster-scope the CLF (my bad, I thought it made sense at the time) and there are several significant problems:

1. The CL singleton is namespace scoped. It's too late to cluster-scope the CL and having the CL and CLF in different scopes makes no sense, to users or to our implementation internals. It *will* bite us in the ass.

2. Cluster scope gives no benefits. We can still support multiple NamespaceLogForwarder CRs in future, it makes no difference if the CLF is cluster or namespace scoped.

3. Namespace scope gives us useful flexibility: we normally deploy logging as a singleton in a single "openshift-logging" namespace and that won't change. However if CL and CLF are namespace-scoped then we *can* deploy independent logging stacks on the same cluster without inteference.

Example: deploy a raw, untested release of logging to an AppSRE or other live cluster for validation, without disrupting the existing customer logging deployment.

Example: paralellize our e2e tests on a single cluster by deploying independent loggings stacks for each test that needs a different configuration.