[cleanup] fix inconsistencies after renaming functions in !35

`geometryTypeFromVertexCount()` was named `geometryTypeFromVertices()`
in earlier versions of merge request !35 and the old name was still used in some places.

See merge request !43

geometryTypeFromVertexCount() was named geometryTypeFromVertices()
during developement and the old name was still used in some places.

Correct two minor errors introduced in !35

See merge request !42

Just in case it gets no longer included indirectly due to future
changes.

Feature/fromvertices

see issue #1 

we move the makeFromVertices implementation into a utility function, which clearly states that it only works up to 3D.

See merge request !35

Do not install `jacobian.mac`

The file is not a header, but a generator for quadrature rules. It is
only useful when building dune-geometry.

See merge request !39

Ansgar Burchardt authored 8 years ago and Christoph Grüninger committed 8 years ago

The file is not a header, but a generator for quadrature rules. It is
only useful when building dune-geometry.

Build `test-nonetype`

See merge request !33

[cleanup] use delegating constructors for AffineGeometry

Since we started to require C++11-compatible compilers, we can now make
use of delegating constructors to remove code duplication and make the
intention of the constructors more clear.

AffineGeometry's constructors always come in pairs: one taking a
ReferenceElement and one taking a GeometryType. Since the GeometryType
is only used to look up a ReferenceElement and then proceed identical to
the former constructor, we can instead delegate the actual construction
from the latter to the former constructor.

See merge request !36

Use Hybrid::forEach instead of wrapper ForLoop

Use `Hybrid::forEach` instead of wrapper `ForLoop`.

See merge request !37

Since we started to require C++11-compatible compilers, we can now make
use of delegating constructors to remove code duplication and make the
intention of the constructors more clear.

AffineGeometry's constructors always come in pairs: one taking a
ReferenceElement and one taking a GeometryType. Since the GeometryType
is only used to look up a ReferenceElement and then proceed identical to
the former constructor, we can instead delegate the actual construction
from the latter to the former constructor.

we moved the implementation of GeometryType::makeFromVertices to
the utitlty function geometryTypeFromVertices and marked it
deprecated.

Please see issue #1

remove generic geometry subdirectory

On the last developer meeting, we agree on the following things:
- The `genericgeometry` subdirectory should vanish in the next DUNE release.
- All content of the namespace GenericGeometry is considered an implemenation detail.

This merge implements these decisions. All functionality that is sitll required is migrated into the appropriate headers in `dune/geometry` and put into the namespace `Impl`. 

**Note**: There is *no transition phase* for the content of the `genericgeometry` subdirectory.

See merge request !34

The only use in the core was in dune-localfunctions and has been replaced by the
reference element and IfTopology.

CodimTable predates the introduction of std::tuple and std::integer_sequence.
Using C++14, it can easily be replaced by these two.

Note: The CodimTable is considered an implementation detail of dune-geometry an
      is removed without any transition phase.