Allow for nested conditions in Launch rules

In addition to the need for an "OR" operator (Allow for "OR" conditions in rules ), being able to nest conditions would be very powerful. For instance, I just did this custom code condition for a client:

This would allow us to move out of custom code conditions, and possibly reduce redundant rules folks might resort to make.