Did you realize? Containers provide AND and OR visibility logic to allow multiple "show-if" conditions to apply...
If you have 2 attributes (the attribute a, the attribute b) and you only want to display controls depending on values from both, you don't need to write a combining rule like the following example:
Containers within containers are AND logic if each container has "show if" or "hide if" for a different attribute.
Containers beside containers are OR logic if each container has "show if" or "hide if" for a different attribute.
That technique can be combined for more complex visibility logic, and I would note that this generally also helps organize similar content together. All content dependent on the first and the second attribute now have reason to be co-located in the interview.
There is no need to create yet another top level attribute with an AND or OR logic just for visibility. Those things clutter up your data model, in any case.