[test][typetraits][warnings] Split the test for deprecated functionality in typetraits.hh into its own testcase.  That way I can simply disable deprecation warnings there.

There was a mechanism with apparently similar goal involving the define
DISABLE_DEPRECATED_METHOD_CHECKS.  However, I could not figure out how that
was intended to work, the only occurances of DISABLE_DEPRECATED_METHOD_CHECKS
were in typetraitstest.hh.  Probably you were supposed to set that define by
hand in your CPPFLAGS, which I consider unacceptable.

It's more CMake style.

This bug could only be found outside Germany :D

Before the test was not active since '#if HAVE_GMP' fails
if the gmp-flags where not added.

most of the tests work. std::complex<GMPField> does not work as expected, but this is
perhaps something we don't want to support. As std::complex does not allow to initialize
with other parameters than the data type itself, we can not initialize from int or other
compatible scalar values. The smae problem occures when interacting with int values directly.

If LAPACK is not available, it return 77 indicating skipped test

Like we do for Autotools.
This is only supported for CMake 3.0 or newer. Oder versions ignore
the property and report the test as failed.

It should be std::endl.
Courtesy of GCC 5-svn, it refuses to compile these.

GCC warns about it.

[parametertree][locale][fs1528] Check ParameterTree::get() with a locale using "," as the decimal seperator.

ParameterTrees are usually read from configuration files.  The format of the
configuration file should not depend on the locale.

For the commandline parser it would likewise be surprising if "progname -param
0.5" stopped working in a german locale.

Not long ago these kinds of errors would not even generate a diagnosis due to
FS#1527.  However, the locale of the program is "C" by default, so probably
not many poeple are actually affected by this problem.  It can happen however
that other libraries linked into the same program set the locale from the
environment.

"Makefile.in", "*.o", etc. need only be listed in the toplevel .gitignore, the
rules are applied recursively.

Test programs etc. should be listed as "/program" in their directory's
.gitignore, so they are not accidentially ignored in a lower level directory.

assert() works only in debug builds (without -DNDEBUG).  Instead, implement
our own check_assert().

Rip out the complete test for eigenValuesNonSym and replace it by the Rosser matrix test from fieldmatrixtest.cc

The old test was complete nonsense: an implementation of some sort of strange
undocumented shape function set that happened to need eigenvalues for something.
Lots of undocumented code, and no checks at all whether the values obtained
by eigenValuesNonSym actually make sense.

Only, for the particular choice of parameters used, eigenValuesNonSym was never
called.  Yes, you read this correctly: these hundreds of lines of code didn't
actually test anything.

The new test is copied form fieldmatrixtest.cc and adapted for DynamicMatrix
types.  It computes eigenvalues of a given 8x8 matrix and compares with the known
results.  Unfortunately, the test matrix is only symmetric.  Tests with more
general matrices are left for another day.

These classes are deprecated, and some of the tests cause
problems with ctest due to a destructor throwing an exception.
It seems easier to remove the tests directly, as the tested code
is deprecated anyway.

testdebugallocator_fail{1..5} are a very special sort of tests,
as in order to pass they are expected to fail with a signal like
SIGABRT or SIGSEGV. While autotools, dont distinguish much
about how a test failed, if it is supposed to fail, ctest
handles signals from the test and distinguishes this from
normal termination with nonzero exit code.

This commit introduces a signal handling in the test itself,
that causes the program to terminate "normally" with a nonzero exit
code instead of passing the signal to the fathering process
(ctest). The signal, which is expected to be received can be set
from CMakeLists.txt via a preprocessor variable.

C++14 will introduce integer/index sequences in the header <utility>.
This patch introduces a backwards compatible implementation similar in
use. However, the implementation differs in the following technical
details:

  - index_sequence is not a template alias for integer_sequence but
  inherits from it

  - make_{integer, index}_sequence are not a template aliases but free
  standing functions

Both differences stem from the absence of template aliases introduced in
GCC aa late as gcc-4.7. This implementation will work in gcc-4.4 and
later.