Refs #22197

Refs #22197

- input workspaces having dx values defined should be accepted even if dx values will not be present in the output workspace depending on the output option
- enhance documentation in terms what happens if dx values are present in the input workspace
- in unit test: making it clear if a variable is a double by using the dot .

Please note that the unit test now fails due to the input workspaces with dx values.

Refs #22197

refs #15175

refs #15175

Looks like the buildservers didn't like me plugging boost::assign::list_of straight into a function. I've moved all calls to it to a separate line assigning to a new variable in each instance

Manual scale factor override is now implemented

Tests have been ported

added 4 of the stitching tests: test_stitching_forces_start_overlap, test_stitching_forces_end_overlap, test_stitching_scale_right and test_stitching_scale_left

Just ran the VS2010 auto formatter over the code to indent things more consistantly

Fixed bug in x-intersect code

Got two more tests working and passing

Quashed a few warnings relating to double and unsigned int64 types