Partial recursion unrolling for PreOrderIter

[gregreich]

Occasionally, I have trees that are very degenerate in the sense that they feature an overwhelming majority of "only-child" parents; let's call those trees "sparse" in this context. In my application, the sparseness is inherent already in the physical domain that I model, and is thus costly to avoid in the code. Now, for large trees, important standard operations that build on recursion—such as the iterators—can blow up the Python recursion stack; at the same time, the latter can no longer simply be increased without tricks (see, for example, this discussion).

One way to avoid this is to "unroll" all those recursions that are degenerate in that they do not incorporate any branching. I have implemented that in PreOrderIter exemplarily, and added some more unit tests that capture cases that haven't been covered before. This partial unrolling implementation is a compromise between loop and recursion: of course, the queue (or the stack) approach could be used even more consequently, eliminating all recursion whatsoever. However, this would particularly complicate the "maxlevel" filtering, having it to rely on (more expensive) calls to the depth property. At the same time, the most obviously unnecessary recursion is effectively avoided, making the iterator significantly more efficient for sparse—yet large—trees.

One final remark about this pull request: For now, I only updated PreOrderIter, for one thing because I mostly use this iterator in my own work, and for another because it is heavily used internally. This latter use is what made me submit this PR: In my understanding, there is no way to "augment" anytree by a new iterator implementation through delegation or inheritance, which also replaces its internal use in standard properties, such as leaves, size, etc.

[coveralls]

coverage: 98.856% (+0.007%) from 98.849%
when pulling 34b38ee on gregreich:main
into 2e0a1b9 on c0fec0de:main.

[gregreich]

any thoughts, maybe @c0fec0de ?