#14772 Python: Add Reservoir.create_multiple_fractures as object method and forward createMultipleFractures to it

RimEclipseCase_createMultipleFractures takes WellPath objects and a
FractureTemplate object instead of names and ids. The
MultipleFractures::Action enum is moved from the Ricf header to
RicCreateMultipleFracturesFeature.h so the object method does not
depend on CommandFileInterface, and is registered as the Python
StrEnum MultipleFracturesAction.

Add RicfForwarding::findFractureTemplate(). RicfCreateMultipleFractures
resolves names/ids and forwards to the object method.

The hand-written Case.create_multiple_fractures(template_id=...,
well_path_names=...) Python wrapper is removed: the generated
Reservoir method has the same name and shadows it. The test is updated
to the object based signature.

ApplicationLibCode/CommandFileInterface/RicfCreateMultipleFractures.h

@@ -20,18 +20,10 @@
 
 #include "RicfCommandObject.h"
 
+#include "FractureCommands/RicCreateMultipleFracturesFeature.h"
 #include "cafAppEnum.h"
-#include "cafPdmField.h"
 
-namespace MultipleFractures
-{
-enum class Action
-{
-    NONE,
-    APPEND_FRACTURES,
-    REPLACE_FRACTURES
-};
-}
+#include "cafPdmField.h"
 
 class RimEclipseCase;
 class RimFractureTemplate;
@@ -52,9 +44,6 @@ public:
     caf::PdmScriptResponse execute() override;
 
 private:
-    bool                 validateArguments() const;
-    RimFractureTemplate* fractureTemplateFromId( int templateId ) const;
-
     caf::PdmField<int>                                     m_caseId;
     caf::PdmField<std::vector<QString>>                    m_wellPathNames;
     caf::PdmField<double>                                  m_minDistFromWellTd;