Description of problem:
Deploying hw event proxy operator on SNO fails

Version-Release number of selected component (if applicable):
Client Version: 4.9.17
Server Version: 4.10.0-0.nightly-2021-12-14-122508
Kubernetes Version: v1.22.1+6859754
hw-event-proxy commit c3f0d2d42c1efade66d8a653cbdf77a2d8fc1f66
hw-event-proxy-operator commit e0a07730cf8ac7da29aa9475bdf5bb316247c233

How reproducible:
Always reproduces

Steps to Reproduce:
0. Deploy bare metal server using ZTP by the files here:
http://registry.kni-qe-0.lab.eng.rdu2.redhat.com:3000/kni-qe/ztp-site-configs/src/helix28-4.10

1. clone the repo from https://github.com/jzding/hw-event-proxy-operator.git run:
2. make deploy
3. oc get nodes and get the name of your SNO
4. oc label --overwrite node <name of worker node> app=local
5. Now from the repo for https://github.com/redhat-cne/hw-event-proxy.git run:
6. make deploy-amq to get the sidecar of cloud native events
7. From the hw-event-proxy-operator repo run:
8. sed -i 's#amqp://amq-router-service-name.amq-namespace.svc.cluster.local#amqp://router.router.svc.cluster.local#' config/samples/event_v1alpha1_hardwareevent.yaml

9. oc apply -f config/samples/event_v1alpha1_hardwareevent.yaml -n hw-event-proxy-operator-system

10. Get the IP addr for the redfish under test, along with the user and password and update them in the tests/e2e/manifest/secret.yaml 
11. oc apply -f tests/e2e/manifest/secret.yaml -n hw-event-proxy-operator-system

Actual results:
New hw-event-proxy pod is not created

Expected results:
we expect a new pod to be added to the namespace in the hw-event-proxy-operator-system with the prefix name hw-event-proxy

Additional info:
Issuing 
oc get HardwareEvent
, and then,
oc get deployment hw-event-proxy -o json
Shows this problem:

 "message": "pods \"hw-event-proxy-5cff9d69c5-\" is forbidden: autoscaling.openshift.io/ManagementCPUsOverride the pod namespace \"hw-event-proxy-operator-system\" does not allow the workload type management",