ClusterLogForwarder configuration by namespace admin so each project can configure their log sink according to their needs and requirements

1. Proposed title of this feature request
ClusterLogForwarder configuration by namespace admin so each project can configure their log sink according to their needs and requirements

2. What is the nature and description of the request?
ClusterLogForwarder is great but requires cluster-admin to configure ClusterLogForwarder based on specific needs raised by the namespace admin.

It would be nice, if instead the namespace admin could create ClusterLogForwarder in it's namespace and configure the log sink for it's namespace without require support/assistance from the cluster-admin to-do so.

That would improve the self-service experience for Cluster Logging and allow log sink configuration based on namespace requirement without the need of a cluster-admin or other elevated role.

3. Why does the customer need this? (List the business requirements here)
Log forwarding becomes a common habit but each namespace has its own requirement for log sink. Having to raise changes and initial configuration with the cluster-admin is disturbing, time-consuming and not in-line with self-service approaches used elsewhere.

With ability to configure ClusterLogForwarder by the namespace admin this will improve the experience and allow each and every project to either send the data to the default sink or otherwise define their own sink, such as external elasticsearch or loki or kafka or whatever else comes to mind.

4. List any affected packages or components.
OpenShift Container Platform 4 - Cluster Logging