Fixing anytree dependency

[erikbosch]

We have started to use 2.9 functionality
Latest is 2.12 but keeping 2.9 for maximum compatibility

Also updating poetry.lock by poetry.lock

[erikbosch]

FYI @sschleemilch @SebastianSchildt

If test works I will merge this for 5.0 and create a new rc. But we can discuss wanted approach for main, I see two main alternatives

• Specifying minimum version that works, in this case 2.9
• Specifying latest and greatest, i.e. what we committers actually use and what is used in CI, in this case 2.12

The latter approach gives less risk for problems as detected by @UlfBj (as we do not test older versions like 2.8/2.9 in CI), but might give more problems if you want to run other tools which does not support 2.12 in the same python env/venv.

[sschleemilch]

Good finding. We should think about pinning dependencies if we encounter something like that again