Description of problem:
The 'vfRange' in NodeState is incorrect when 'pfName' is not specified in node policy CR.
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. launch the operator, and apply the following node policy.
```
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
  name: policy-net-2
spec:
  resourceName: nic2
  nodeSelector:
    feature.node.kubernetes.io/network-sriov.capable: "true"
  priority: 99
  mtu: 9000
  numVfs: 4
  nicSelector:
    vendor: "8086"
    rootDevices: ['0000:86:00.1']
```

2. Check the node state of the worker node.
```
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodeState
metadata:
...
  name: nfvpe-25.oot.lab.eng.bos.redhat.com
  namespace: openshift-sriov-network-operator
...
spec:
  dpConfigVersion: "4454192"
  interfaces:
  - mtu: 9000
    name: ens803f1
    numVfs: 4
    pciAddress: 0000:86:00.1
    vfGroups:
    - deviceType: netdevice
      resourceName: nic2
      vfRange: 0-0
```

3.

Actual results:

The 'vfRange' was '0-0'.

Expected results:

The 'vfRange' should be '0-3'.

Additional info: