Remove all remnants of old build-system(s)

The m4/ directory is left since other DUNE modules that include
opm-core include scripts from this directory; if we delete them then
these modules no longer work. They are not necessary for building
with CMake.
Barebones CMake configuration file
Ignore files generated by the CMake scripts
Define function to write a list of variables to config.h

A fundamental problem with the configure_file() command is CMake is that
the author of the template file config.h.in must know which variables
all modules need to have defined, and this is not easily communicated.

The idea behind this function is: Each Find-module can return a list of
variables that it has filled with probed values, and that should be
written to config.h, which is again included by the header file of this
module.

Each project thus defines its own config.h file, which is common between
all module's headers.
Put results of platform checks in configuration header

Various features in the code base will be enabled depending on the
values written by the build system in here.
Remove files which are not part of the official library

Some files are distributed with the source, but does not end up in the
final shared object. These files are captured by the glob, so we have
to remove them afterwards. (There are fewer of these files than
explicitly list all files that should be included in the build).
Added library version
Compile with C++0x/11 if available

We want to compile with the -std=c++0x since DUNE uses this settings and
we need to use the same ABI as that one if we are going to link with it.

Find module is a copy of the one in cmake/modules in (the cmake branch of)
dune-common.
Add options without repeating them on the command-line
Don't repeat option if already present
Append standard variables to project after finding package

Normally a package returns a set of standard variables such as
Xxx_INCLUDE_DIRS. Adding this to a list that is collected for the
project amounts to a bunch of boilerplate which can rather be
encapsulated in a macro.
Use generic boilerplate macro to include packages
Link against BLAS+LAPACK numerical libraries

The tests for these packages are part of the standard CMake installation
so there is no config modules for them here.
Link against XML parser library
Link with C++ Boost library
Check for dynamic linking of Boost::Test library

BOOST_TEST_DYN_LINK must be defined if you are *building* Boost::Test as
a shared object, and the client programs must also include this option
when they use the header files, to link to it correctly.
Probe for SuiteSparse libraries

Search for modules in this library in the same style as Boost; by
specifying a list of components. If all on the list is present, then
a list of libraries to link with, is returned.
Link with UMFPACK in SuiteSparse if available
Search module for SuperLU library

Original downloaded from:
  <https://svn.dune-project.org/svn/dune-istl/branches/cmake/cmake/modules/FindSuperLU.cmake>

Renamed to all capitals in name so that the name of the package is
consistent with the variables it returns.
Add define for SuperLU later than 2005

This is a prerequisite for using the find module, but some code
explicitly check this macro anyway.