1. Proposed title of this feature request

The OCP metrics has node-exporter with the `--no-collector.cpufreq` option which prevents it from reporting CPU frequencies on baremetal nodes. These Cpu frequencies metrics are required when doing inferencing of advanced energy aware scheduling options, or when doing energy profiling for CNF applications based on their actual utilization when running in baremetal nodes.

2. What is the nature and description of the request?

One of the following:

• To remove a `node-exporter` Pod command line argument which disables an otherwise default collected metrics of the`cpufreq` module
• To provide an API on the CR to enable `cpufreq` module in node-exporter. (Even better if provides the ability to enable optional native modules of node-exporter)

3. Why does the customer need this? (List the business requirements here)

This type of parameter is required when training ML models to apply AI for smart placements and optimization of workloads for energy reduction or energy optimization on a mobile network (CU, Core and MEC).

Similar benefits could be achieved on workloads for for HPC and FSI use cases.

4. List any affected packages or components.

Needs to remove a `node-exporter` Pod command line argument which disables an otherwise default collected metric.