Fixed order in configuration

[fsimonis]

The formatter should reorder the configuration sections into the general order:

• log
• profiling
• data
• mesh
• participant
• m2n
• coupling schemes

Furthermore, we could order subtags of participants and coupling schemes consistently:

participant

• provide-mesh
• receive-mesh
• read-data
• write-data
• mapping
• other (exporter, watchpoint)

coupling scheme

• participants
• exchange
• time window size
• stopping criteria: max time windows / max time
• iterations (max min)
• convergence criteria
• acceleration

In acceleration tags we could sort data to the beginning.

  <coupling-scheme:parallel-implicit>
    <participants first="Fluid" second="Solid" />
    <exchange data="Force" mesh="Solid-Mesh" from="Fluid" to="Solid" />
    <exchange data="Displacement" mesh="Solid-Mesh" from="Solid" to="Fluid" />
    <time-window-size value="0.01" />
    <max-time value="5" />
    
    <max-iterations value="50" />
    <relative-convergence-measure limit="5e-3" data="Displacement" mesh="Solid-Mesh" />
    <relative-convergence-measure limit="5e-3" data="Force" mesh="Solid-Mesh" />
    <acceleration:IQN-ILS>
      <data name="Displacement" mesh="Solid-Mesh" />
      <data name="Force" mesh="Solid-Mesh" />
      <preconditioner type="residual-sum" update-on-threshold="false" />
      <filter type="QR2" limit="1e-2" />
      <initial-relaxation value="0.5" />
      <max-used-iterations value="100" />
      <time-windows-reused value="15" />
    </acceleration:IQN-ILS>
  </coupling-scheme:parallel-implicit>

[fsimonis]

Decision:

We want this.
However, comments need to make sense after the formatting.

[fsimonis]

FYI @orlandoisepic