using host tags AND storage tags, even if they are correctly assigned, deployments fail

> ok, when a deployment in a dedicated resource fails in general other resources will be queried to see if deployment is possible there. So the tagging problem is not specifc to the dedication (I think).

Ok, so then what would be the proper way to solve this issue? At the moment I found a working setup like this: both ssd storages, from both hosts, have the same tag, ssd, and both hdd storages have hdd. Offerings are created with storage tag. If I deploy a vm AND choose the host manually, it uses the correct storage, depending on the offering that I choose. This is ok, but I cannot find a way to have ACS choose the host automatically - if I use host tags AND storage tags, even if they are correctly assigned, all deployments fail.

_Originally posted by @tdtmusic2 in https://github.com/apache/cloudstack/discussions/11080#discussioncomment-13570015_

Review the deployment and tagging discussion in issue #11083 and the linked pull request #13951, along with the original discussion #11080. The work is done when automatic host selection succeeds while honoring both host tags and storage tags, as manual host selection already does.

Written by the indexing model from the issue text.