Understanding and controlling multi-GPU behavior

**Describe the support request**
Hi there, this is a bit of a follow up on my previous issue (https://github.com/intel/intel-device-plugins-for-kubernetes/issues/1769).

What is the behavior of the GPU plugin on a multi-Intel-GPU system when [installing with NFD](https://github.com/intel/intel-device-plugins-for-kubernetes/tree/main/cmd/gpu_plugin#install-with-nfd) where an app requests a GPU with (assume only i915 driver enabled on host):

```
resources:
limits:
gpu.intel.com/i915: 1
```

For example:

* Which GPU device will be used for the first app requesting a GPU? Is there any way to control this?
* It appears from [the docs](https://github.com/intel/intel-device-plugins-for-kubernetes/tree/main/cmd/gpu_plugin#operation-modes-for-different-workload-types) that when using `sharedDevNum=N` all slots will be filled on one of the GPUs before apps are scheduled on the next GPU? Is that right?

**System (please complete the following information if applicable):**
- OS version: Ubuntu 22.04, 24.04
- Kernel version: 6.8.0-40-generic
- Device plugins version: v0.30.0
- Hardware info: iGPU and dGPU