Now, the label is used instead of the entry widget for mandatory and
default values styling.

(It is not recognized as property but rather as a child node so that the
syntax stays easy and the same for multiple file types - just supply
multiple <option> nodes)

- The commanding lambda now correctly receives a constant index and
  therefore the correct tab name is changed.
- When previewing an INI file where all that has been done was to open
  an application without changing anything, it is now still marked as
  unsaved (because although it might save a click in special situations
  it does not make sense to have a different logic than in the GUI and
  can only be confusing).
- Default names now get an .ini file extension i. e. unsaved(1).ini.
- Path/filename splitting is done once on file changes and then reused
  from outside without asterisk shuffling.
- Minor logic cleanup, consts and styling

renamed the undst filter into shift, removed time restrictions on the time filters (as this is not applicable)

A bug has been found where the user manually edits the run path in a workflow and makes it invalid...

The problem is that the command that should run does not run and we show
an error message saying that the command could not be found when it fact
it was an invalid run path... A hacky way of catching this kind of
errors has been implemented, but it wold be better to be able to show an
error message in the log window instead of only in the status bar.

Some keys were missing, some documentation was missing, etc

Unfortunatelly, it was not possible to rely on the '@' template
parameter, so lots of XML is duplicated...

Manually entering anything other than ${inifile} was preventing the
simulation from running (the ini file could not be found anymore), so
for now this possibility has been removed (commented out in the XML). At
some point, we could decide to re-implement this feature but we would
need to make sure it works fine (so the simulation really runs from the
right path and the inif ile would be transparently loaded into the
configuration panel. Adding a file selector would almost be mandatory as
well as the possibility to drag n drop files into this entry widget)

And some mandatory parameters that were not tagged as such have been
properly marked as mandatory