#14484 Orion Events: parse and apply data filter

Add a typed FILTER declaration to the ORIONEVENTS 2.0 grammar, e.g.
FILTER POROPERM = "PORO > 0.4 AND PERMX > 100.0". A PERFORATION event
references it with FILTER=POROPERM or supplies an inline quoted
expression. When applied, each used filter is materialized as a
case-level combined data filter (one property filter per term, one-sided
inclusive bounds, AND/OR combine mode) and attached to the perforation.

Unqualified result names are searched in STATIC_NATIVE, DYNAMIC_NATIVE
then GENERATED results; a TYPE. qualifier restricts the search. Missing
results raise before any event is applied. apply_orion_document gains an
optional case= parameter defaulting to the project's first case.

RimWellEventPerf carries a RimCellFilter ptr-field with scriptable
AddFilter/cell_filter methods, and the filter is copied onto the
RimPerforationInterval when the timeline materializes completions.

ApplicationLibCode/ProjectDataModel/WellEvents/RimWellEventTimeline.cpp

@@ -493,6 +493,11 @@ bool RimWellEventTimeline::applyPerfEvent( const RimWellEventPerf& event, RimWel
         perfInterval->setCompletionNumber( event.completionNumber() );
     }
 
+    if ( event.cellFilter() )
+    {
+        perfInterval->setCellFilter( event.cellFilter() );
+    }
+
     // Set the custom start date based on the event date
     perfInterval->enableCustomStartDate( true );
     perfInterval->setCustomStartDate( event.eventDate().date() );