fix: Ignore devices not managed by DraNet in ResourceClaim

[gauravkghildiyal]

This should help enable use cases involving device topology alignment.

Currently, we fail to process ResourceClaims that have devices from distinct drivers like the example below, since we don't recognize the customgpu0 device.

apiVersion: resource.k8s.io/v1beta1
kind: ResourceClaim
metadata:
  name: my-claim
spec:
  devices:
    constraints:
    - matchAttribute: resource.kubernetes.io/pcieRoot
      requests:
      - nic-request
      - gpu-request
    requests:
    - allocationMode: ExactCount
      count: 1
      deviceClassName: dranet-cloud
      name: nic-request
    - allocationMode: ExactCount
      count: 1
      deviceClassName: gpu.nvidia.com
      name: gpu-request
status:
  allocation:
    devices:
      results:
      - adminAccess: null
        device: eth1
        driver: dra.net
        pool: my-node
        request: nic-request
      - adminAccess: null
        device: customgpu0
        driver: gpu.nvidia.com
        pool: my-node
        request: gpu-request

[aojea]

great catch, I thought there was something before like this, or I misremember or at some point I deleted it, but this is really needed

[michaelasp]

Ah this is the reason why I had to split my example into 2 separate claims which the pod then asked for. Good fix!