Grouped conditional logic and negation in the rules engine

The rules engine currently supports only flat, single-condition logic, so operators can't express compound criteria in one rule. There's no way to group conditions with AND/OR, nest groups, or negate a condition (NOT / exclusion). As a result, any logic more complex than a single condition has to be split across multiple near-duplicate rules — which multiplies setup time, invites inconsistencies, and compounds across organizations that mirror rules across many accounts. A common case is targeting multiple OTAs in one rule: today that requires a separate rule per channel because the conditions can't be combined.

Requested Enhancement:

• Support grouped conditional logic — combine conditions with AND/OR and nest groups within a single rule.

• Support negation — allow a condition to be expressed as NOT / exclusion (e.g., all channels except one, or fire unless a condition is met).

• Handle channel-specific condition validity within compound rules: Google (GMB) has no cleanliness sub-score, and a normalized Airbnb 4/5 vs. a Booking 8/10 can mean different things against a single threshold — so warn, auto-skip, or scope conditions per channel where a sub-score or scale doesn't apply.

Benefit: Grouped logic and negation would let a single rule express what today takes many, cutting duplicate rule creation, reducing inconsistencies across channels and accounts, and lowering setup and maintenance overhead. Multi-OTA targeting becomes a natural outcome rather than a special case, and operators gain the expressiveness to model real-world routing and exclusion logic in one place.