gpu: change 'none' allocation policy

[tkatila]

With shared-dev-num and multiple i915s in the resource request, try to find as many individual GPUs to expose to the container.

Previously, with multiple i915 resources, it was typical to get only one GPU device in the container.

Fixes: #1377

[codecov-commenter]

Codecov Report

Merging #1398 (e20257f) into main (0bf4cd0) will increase coverage by 0.25%.
The diff coverage is 100.00%.

❗ Current head e20257f differs from pull request most recent head db7cd12. Consider uploading reports for the commit db7cd12 to get more accurate results

@@            Coverage Diff             @@
##             main    #1398      +/-   ##
==========================================
+ Coverage   50.89%   51.14%   +0.25%     
==========================================
  Files          44       44              
  Lines        4985     5005      +20     
==========================================
+ Hits         2537     2560      +23     
+ Misses       2302     2300       -2     
+ Partials      146      145       -1     

Impacted Files	Coverage Δ
cmd/gpu_plugin/gpu_plugin.go	88.28% <100.00%> (+1.06%)	⬆️

... and 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[eero-t]

Only trivial comments...

[eero-t]

@uniemimu Can this change interfere with: https://github.com/intel/platform-aware-scheduling/blob/master/gpu-aware-scheduling/docs/usage.md#enforcing-same-gpu-to-multiple-containers-within-pod ?

[uniemimu]

@uniemimu Can this change interfere with: https://github.com/intel/platform-aware-scheduling/blob/master/gpu-aware-scheduling/docs/usage.md#enforcing-same-gpu-to-multiple-containers-within-pod ?

No, this is totally separate from GAS.