[FEATURE] Support AND operations on Rollover conditions

[tandonks]

Is your feature request related to a problem?

Currently, rollover conditions in ISM only support an OR relationship. This means a rollover is triggered as soon as any condition (age, size, docs, etc.) is met.

Users who want rollover to occur only when multiple conditions are satisfied together (e.g., both index age AND index size) cannot express this directly.

To work around this limitation, users add additional states and transition conditions in their ISM policy to enforce an AND-like behavior. This leads to more complex policies, reduced readability, and increased maintenance overhead.

What solution would you like?

Add native support for AND operations between rollover conditions, enabling users to specify that rollover should occur only when all specified conditions are met. We can introduce an additional flag possibly. which could help identify if the customer wants the conditions to be evaluated using AND or OR logic

What alternatives have you considered?

State-based workaround:
Adding a separate state with transition conditions to emulate an AND behavior. This works but is cumbersome and unintuitive.

External automation:
Using scripts or monitoring systems to check multiple conditions and trigger manual rollover. This adds operational overhead and removes the convenience of built-in ISM logic.

Do you have any additional context?

• Customers often want to ensure both an index age threshold and a size threshold are met before rollover, especially in ingestion-heavy or cost-sensitive environments.
• Supporting AND logic makes ISM policies cleaner and more aligned with typical lifecycle management expectations found in similar systems.
• The proposed flag makes the feature opt-in and backward compatible.