Use AND to combine different volume filter keys

[simonbrauner]

Fixes: #26786

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?

Volume filters with different keys are combined with AND instead of OR

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

[simonbrauner]

OR is currently used, and by changing it to AND would make it consistent with Docker.

[packit-as-a-service]

Cockpit tests failed for commit 9efd4d8. @martinpitt, @jelly, @mvollmer please check.

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

[mheon]

Frankly this is making me regret ever merging label!= support

[Luap99]

How does it behave with containers, images? Whatever we end up it must be consistent for all filtering.

[simonbrauner]

How does it behave with containers, images? Whatever we end up it must be consistent for all filtering.

AND is also used for filters of different keys when filtering images, containers, and pods.