integer types in interface cleaned up, to reduce warnings related to comparison between signed and unsigned integers

The previous test refined all elements using local adaptivity. The new
test results in a leaf view with elements of different levels and tests
more things. The bug fixed in 6e374b7d
would have been revealed.

The previous implementation had a sign mistake and thus only worked
for intersections connecting elements on the same level. The new
implementation works for adaptive grids as well.

Note: this is a backward compatible change. The growth insertion index
can now be used conveniently to attach user data to the new element.

Each element has a growthInsertionIndex that can be queried using a grid method
with the same name. This index is only valid between calling grow() and postGrow()
and only for elements that have been inserted using the grids insertElement method.
It can be used to attach user data to an element inserted with the insertElement method,
because we don't know at insertion time (before calling grow()) which index or id
the element will have in the grid. The concept is very similar to the insertionIndex
of the factory with the difference that the validity of the index is only temporary.

When inserting two element that share a new vertex this vertex was inserted twice
resulting in a disconnected grid. The check if a vertex is already inserted was
already in place, however the map had the wrong scope and the pointer written
in the map was a pointer to the grid entity not the entity in the to-be-inserted queue.

This silences a few warnings when compiling with -DNDEBUG.

When global refining not all isNew markers were removed.
This also caused a bug when mixing growth and adaptivity as the
isNew marker is also used for newly added elements through growth.

Only leaf vertices can get a new position. However this
triggerts that the vertex' position on all levels will
be changed accordingly.

Add a setPosition test.

For consistency with the factory.

When the final insertion level for vertices and elements was
determined for an element that is unconnected to the elements
of the current grid the level was initialized to numerical_limits::lowest.

This makes sure the lowest level is zero

Adds a test that checks inserting an unrelated element.

We use the ID later to determine whether new vertices are
used by multiple elements.

Using up ids for entities that are not inserted in the end made the idSet fail
to contain all entities for some reason.