Fix Docker API DeviceMapping for CDI devices

[Honny1]

Checklist

Ensure you have completed the following checklist for your pull request to be reviewed:

• Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
  commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
  the sign-off email address. See CONTRIBUTING.md
  for more information.
• Referenced issues using Fixes: #00000 in commit message (if applicable)
• Tests have been added/updated (or no tests are needed)
• Documentation has been updated (or no documentation changes are needed)
• All commits pass make validatepr (format/lint checks)
• Release note entered in the section below (or None if no user-facing changes)

Does this PR introduce a user-facing change?

Compat API Container create no longer turns CDI-qualified HostConfig.Devices entries into invalid `host:container:permissions` strings when optional fields are empty, so compose-style clients can pass CDI selectors reliably. DeviceRequests with driver cdi are now matched case-insensitively.

[Luap99]

an e2e compose test like test/compose/cdi_device/docker-compose.yml would make sense, I guess just add a second device to the config and then pass it as normal device in compose?

[Luap99]

do you have any references why this should support upper case?

https://github.com/docker/cli/blob/950401cf07cf590e921d94ace7311977dd582a3c/cli/command/container/opts.go#L606-L609
https://github.com/docker/compose/blob/d518da24193f88d9ecf8e847fe2f89b2344b6405/pkg/compose/create.go#L684-L687
suggest they send the string lowercase

[Honny1]

My original plan was to take a defensive approach, but I realize now that it doesn't make sense. I will fix it.

[Honny1]

an e2e compose test like test/compose/cdi_device/docker-compose.yml would make sense, I guess just add a second device to the config and then pass it as normal device in compose?

I'm not sure about this. Newer versions (since docker/compose#12184) of Compose send CDI devices through cc.HostConfig.Resources.DeviceRequests, so the new test will always pass.

[Honny1]

I am not sure if this change fixes the reported issues, as I cannot directly verify them. The main goal of this change is to make defensive improvements for edge cases that might occur with older versions of Compose or other clients.

[mheon]

It seems like a reasonable change regardless. I wonder if the people seeing this are all on Compose v1? We dropped all our tests for that...