Draft: dune-common should not depend on dune-typetree

Summary

In dune/python/common/dimrange.hh a dependency to dune-typetree is introduced by including typetree headers. This makes the development of typetree complicated, since changes in typetree influence the bahavior of upstream files. Thus, I may get an error in e.g. dune-function, in a header provided by dune-common that something is wrong in dune-typetree.

A specialization of the class DimRange should be done directly in dune-typetree and not within dune-common.