refs #7110

Fixing Crystal, Geometry, Kernel and WorkflowAlgorithms.

Signed-off-by: Karl Palmen <karl.palmen@stfc.ac.uk>

and not as empty strings in file names.

for suggestions of workspace names. The interface uses suggestWorkspaceName(..) method to generate the output file names.

This reverts commit c3722b3c.

It looks like the original commit of this was deleted after it had
already been pushed up, which has made bad things happen.

Ensure that input into a MultipleFileProperty properly survies a "round
trip", i.e. what you put in is what you get out, and that using the output
again, as input into another MultipleFileProperty gives the same results.

Proper functionality in a large number of use cases is assured by vastly
improved coverage of unit tests, which was lacking previously.

Simplify parts of the MultipleFileProperty class, including the filename
generation functors I introduced that weren't doing anybody any favours.

This reverts commit 4fe9cd9d, and fixes
tests.

This reverts commit a9c8a59a.

Allow filenames specified with the format <<short><operator>>...<short>
where:

<short> = <dir><inst><underscore><runs><ext>
<operator> = "+" or ","
<runs> = lists and/or ranges of (possibly added) runs e.g. "12,13+14,15:20".

See header file of MultipleFileProperty for more info on syntax.

This enables workspaces loaded through the algorithm to have a history that
can be used to reproduce the workspace properly.

MWRunFiles widget of LoadDialog now remembers the exact text a user typed -
in this way any user who types "INST0-50", clicks "Run" and reopens the
dialog is not met by a huge string containing a list of all 51 fully
resolved files, but rather their original input.

Changed the vector<vector<string>> templated versions of the toString and
toValue functions to accept customised delimiters.  This enables us to add
an option for the user to turn off multifile parsing if they are crazy
enough to want to load files with a plus or a comma in their path.

Changed the inner workings of Load for multi files.  No longer calling sub
algorithms with setChild or alwaysStoreInADS.  All workspaces are
essentially created outside the ADS and managed by the algorithm, right up
until the OutputWorkspaces are set.

Tests added where appropriate, but the majority of parsing cases are already
covered by MultiFileNameParser.

Where no instrument is specified in the string to be parsed, the default is
taken from the ConfigService and used instead.

Incorrectly diagnosed the problem with the make_pair errors.  The first
instance of make_pair was okay to be left in, just minus the template
parameters.  The second instance was unnecessary anyway, as the constructor
could be used to init the object in that case.

Removing template arguments from call to std::make_pair.

std::make_pair does not seem to have overloaded versions for const paramters
in gcc.

Added a "suggestWorkspaceName" function to the MultiFileNameParsing
namespace, which takes in a vector of filenames, and returns a string which
we can use as a workspace name for the loaded files - assuming they are to
be added or merged together in some way to form a single workspace.

MultiFileProperty changed to store a vector of vectors of file names. File
names that share a vector are to be added. Old functionality can be produced
by calling "flattenFileNames".  See source code for more info.

MultiFileProperty was used in one place previously (MDMergeFiles), this has
been modified to relect these changes.

Load now implemented in terms of MultiFileProperty, though its interface is
unchanged.  "Filename" input is now parsed as a multi file, and if that
fails old functionality is attempted.  Error reports will output the result
of both attempts.

Some additional template specialisations / "toString" overloads
surrounding the Property class heirachy were necessary to properly support
std::vector<std::vector<std::string> >.

Added a more robust run string parser, with better validation / error
messages.  Will make implementation of multifilename parser simpler, which
is to follow shortly.

This will be used to parse multi filename strings entered by user.
More to follow.  Refs #1419.