Add treePath() as alias for hybridTreePath()
There is no ambiguity anyway, because no other tree path
implementation is created by a similar function. This hides
some implementation detail (the fact that there are more tree path
implementations) from the user and creates a tree path that just works.
Since - conceptually -
HybridTreePath can replace all other
implementations, this can be viewed as first step into this