DRA cross-driver mismatch: GPU/Gaudi publish pciRoot as driver-scoped key instead of well-known resource.kubernetes.io/pcieRoot

[yuanwu2017]

Intel GPU and Gaudi drivers publish PCI root as an unqualified attribute name pciRoot in ResourceSlice device attributes.
In DRA, unqualified names become driver-scoped (for example gpu.intel.com/pciRoot), while other components (for example DRAnet) use the well-known key resource.kubernetes.io/pcieRoot.
Because the keys differ, matchAttribute cannot match across drivers.

Problem

Published key from Intel driver: gpu.intel.com/pciRoot (or gaudi.intel.com/pciRoot)
Published key from DRAnet: resource.kubernetes.io/pcieRoot
Result: cross-driver constraints using matchAttribute fail due to key-name mismatch
Expected behavior
Both Intel drivers should publish PCI root using the well-known key:
resource.kubernetes.io/pcieRoot

Why this matters
Using the well-known attribute key allows matchAttribute-based alignment constraints to work consistently across different DRA drivers.

[byako]

The upcoming release later this month introduces both - the resource.kubernetes.io/pcieRoot and resource.kubernetes.io/pciBusID .