Enable process metrics in CI

[jichenjc]

What happened?

https://github.com/sustainable-computing-io/kepler/issues/1153 caused some issue , we should enable this in the CI in order to make sure it's not break

What did you expect to happen?

enable the CI with ENABLE_PROCESS and ENABLE_VM

How can we reproduce it (as minimally and precisely as possible)?

check https://github.com/sustainable-computing-io/kepler/issues/1153

Anything else we need to know?

No response

Kepler image tag

Kubernetes version

$ kubectl version
# paste output here

Cloud provider or bare metal

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Kepler deployment config

For on kubernetes:

$ KEPLER_NAMESPACE=kepler

# provide kepler configmap
$ kubectl get configmap kepler-cfm -n ${KEPLER_NAMESPACE} 
# paste output here

# provide kepler deployment description
$ kubectl describe deployment kepler-exporter -n ${KEPLER_NAMESPACE} 

For standalone:

put your Kepler command argument here

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)