Refs #13262

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

It seems older boost::date_time versions accepted just dates from
a format string, whilst the newer ones do not. We'll be strict and
require a time from all.
Refs #9227

Refs #9227

Refs #9059

Thisgs to note:
 * C2450 warnings have been suppressed when including Poco headers
   that inherit from std::stream
 * Boost date_time no longer accepts just a date for an ISO date/time
   string

Previously the precision of these would be the nearest second as
the setting went via the DateAndTime::toISO8601String() method,
which truncated the time even if it had a better precision than
that (as the SNS files do). This then caused some oddities when
viewing logs because they do preserve the incoming precision.

DateAndTime::toISO8601String() now preserves the nanosecond precision
of the underlying DateAndTime class.

This reverts commit 1a777402.

The addition of these special methods had a negative impact on a number
of performance tests. Presumably they put a stop to some optimisation that
the compiler was able to do with the implicitly generated versions.

in DateAndTime methods.

in DateAndTime methods.

in DateAndTime methods.

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

The issue was that it couldn't find the python pyd files.
They are now copied into the mantid package instead of being moved. In the
process of this there was some CMake stuff that was duplicated so that
has been removed and a single function used.

Enabled an ARG file to be loaded by correcting and warning about invalid date contained therein. Also enabled unit test that uses this file.

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

Rename Framework code directory to just that. Also delete Main and VS & Eclipse project file. Re #1881.