refs #6667 Instrument parameters modified to take some properties

from dgreduce
refs #6667 first steps in taking all parameters from dgreduce

and moving them into IDF_Parameters.xml
refs #6667 Changed ExperimentInfo::populateInstrumentParameters

to understand booleans, though no unit tests found for populateInstrumentParameters to check this stuff works properly
refs #6667 Exported parameter type from the parameter map

Very ugly done, as python should be able to retrieve the value and type together. But can not find better way at the moment.
refs #6667 Minor changes to export parameter type

and substitution dictionary in DirectEnergyConversion
refs #6667 Failed attempt to build getParameterType test
refs #6667 finally correct test verifying the component type name
refs #6667 Hopefully working solution with Parameter-based file

where all default keys are obtained from Par.xml.
+ int parameter is added to xml parcer.

Need tests and routines, accepting parameters from the arguments.
Merge branch 'master' into feature/6667_ISISReductionInMantid
refs #6667 more changes to parameters and some unit tests attempts
refs #6667 DirectEnergyConversion accepts external parameters

and have number of unit tests enabled testing this functionality. DAE name property imported from Mantid Facility (for qtiGenie to work)
refs #6667 intermediate checkout

some unit tests run and ready to run system tests
refs #6667 diagnose seems work
refs #6667 Intermediate checkout

Old system test for MAPS runs with modified DirectEnergyConversion
Merge branch 'master' into feature/6667_ISISReductionInMantid
refs #6667 Maps system tests run but do not pass

Both old and new tests failing, which is probably due to different defaults
refs #6667 All generally works but constants are missing.
refs #6667 The run data look very close to each other (MAPS)

but not yet identical -- diag seems a bit different
refs #6667 Maps reduction works

But there is subtle difference in reduction results

the difference does not have big physical sense, as the relative values of differences are small, but still unclear why it is present at all.

The CheckWorkspacesMatch got possibility to analyze relative error together with the absolute error to understand the difference better
LoadMask.cpp in the ISIS part has been changed to report loaded masks on debug level rather then notice as the messages in the log complicate understanding of what is going on.
refs #6667 Minor changes for niceness