[Bug]: Ressource restriction for CI/CD affects other installations as well

[widhalmt]

Please try to fill out as much of the information below as you can. Thank you!

• Yes, I've searched similar issues on GitHub and didn't find any.

Which version contains the bug?

No response

Description

I guess the code from https://github.com/NETWAYS/ansible-collection-elasticstack/blob/main/roles/elasticsearch/tasks/elasticsearch-security.yml#L438 down is too generic. The intention was to restrict resources when running in CI/CD pipelines. But we change the behavior for other installations as well.
Maybe we should introduce a new variable we set in every molecule scenario?

To Reproduce

No response

Your Environment

n/a

[widhalmt]

Just found more ansible_virtualization_type == "container" or ansible_virtualization_type == "docker" in when clauses. Some of them might actually make sense, other might interfere with different kinds of setups.