#13273 Well Event: Support completion number on perforation events for COMPLUMP

Add a completion_number parameter to the add_perf_event Python API
(AddPerfEvent scriptable method) and a matching field on
RimWellEventPerf. When a timeline perforation event is materialised into
a RimPerforationInterval, a non-zero completion number is copied across,
so it flows through the existing completion-data path onto
RigCompletionData.

The schedule generator now emits COMPLUMP alongside COMPDAT: COMPDAT
generation is folded into generateCompletionsForWell, which computes the
completion data once and builds both keywords from it via the existing
RimKeywordFactory::complumpKeyword (added in #13273). COMPLUMP only
produces records for perforations that have a completion number and is
merged across wells like COMPDAT.

ApplicationLibCode/ProjectDataModelCommands/RimcWellEventTimeline.cpp

@@ -58,6 +58,7 @@ RimcWellEventTimeline_addPerfEvent::RimcWellEventTimeline_addPerfEvent( caf::Pdm
     CAF_PDM_InitScriptableField( &m_skinFactor, "SkinFactor", 0.0, "", "", "", "Skin Factor" );
     auto defaultState = RimWellEventPerf::State::OPEN;
     CAF_PDM_InitScriptableField( &m_state, "State", defaultState, "", "", "", "State" );
+    CAF_PDM_InitScriptableField( &m_completionNumber, "CompletionNumber", 0, "", "", "", "Completion Number (for COMPLUMP, 0 = none)" );
 }
 
 //--------------------------------------------------------------------------------------------------
@@ -84,6 +85,7 @@ std::expected<caf::PdmObjectHandle*, QString> RimcWellEventTimeline_addPerfEvent
     event->setDiameter( m_diameter() );
     event->setSkinFactor( m_skinFactor() );
     event->setState( m_state() );
+    event->setCompletionNumber( m_completionNumber() );
 
     return event;
 }