Review applications parameter order

Summary

One common confusion from users that I see when doing OTB workshops is that some applications' parameters are all the way at the bottom of the parameters list. This is not a problem in cli but shows up in gui. For example EdgeExtraction:

This MR changes the order of a few parameters to roughly follow the convention: start with mandatory parameters related to I/O. For example EdgeExtraction becomes:

Rationale

Better otbgui UX. User intuition is "higher parameters are more important".

Implementation Details

Depends on !273 (merged) to avoid a git conflict. I will change the target branch of this MR to develop when it's merged.

Copyright

The copyright owner is CNES and has signed the ORFEO ToolBox Contributor License Agreement.

---

Check before merging:

• All discussions are resolved
• At least 2 votes from core developers, no vote.
• The feature branch is (reasonably) up-to-date with the base branch
• Dashboard is green
• Copyright owner has signed the ORFEO ToolBox Contributor License Agreement

Modules/Applications/AppClassification/app/otbDSFuzzyModelEstimation.cxx

@@ -140,6 +140,9 @@ private:
     AddParameter(ParameterType_StringList, "plasup", "Plausibility Support");
     SetParameterDescription("plasup", "Dempster Shafer study hypothesis to compute plausibility");
 
+    AddParameter(ParameterType_OutputFilename, "out", "Output filename");
+    SetParameterDescription("out", "Output model file name (xml file) contains the optimal model to perform information fusion.");
+
     AddParameter(ParameterType_String, "cri", "Criterion");
     SetParameterDescription("cri", "Dempster Shafer criterion (by default (belief+plausibility)/2)");
     MandatoryOff("cri");
@@ -167,9 +170,6 @@ private:
     AddParameter(ParameterType_Bool,"optobs","Optimizer Observer");
     SetParameterDescription("optobs","Activate the optimizer observer");
 
-    AddParameter(ParameterType_OutputFilename,"out","Output filename");
-    SetParameterDescription("out","Output model file name (xml file) contains the optimal model to perform information fusion.");
-
     // Doc example parameter settings
     SetDocExampleParameterValue("psin", "cdbTvComputePolylineFeatureFromImage_LI_NOBUIL_gt.shp");
     SetDocExampleParameterValue("nsin", "cdbTvComputePolylineFeatureFromImage_LI_NOBUIL_wr.shp");