AutoSize calculations can sometimes never reach a stable state

[smoogipoo]

Very easy to replicate with the results screen statistics in lazer: https://drive.google.com/file/d/14bpey-ofUjQGTJJSTeE6nysUIdrOgoh0/view?usp=sharing

Possibly due to FP precision loss, autosize probably shouldn't consider changes in size by such small amounts.

[EVAST9919]

I've stumbled upon a similar (same?) issue with autosized FillFlowContainers and it indeed looks like a precision issue somewhere. In this case parent's autosize depends on children positions and their position depends on size of the parent.
Here's the flow of events:

1. flow layout isn't valid, call PerformLayout
2. this will invalidate childrenSizeDependencies in CompositeDrawable (which FlowContainer is)
3. computing autosize will perform Invalidation.DrawSize and invalidate flow layout
4. call PerformLayout again, now children have slightly different positions
5. autosize will be calculated a bit differently and so are the children positions later

And we are stuck in this loop until we reach the stable state which may or may not happen. Stable state is being reached by praying that all the children won't have different positions calculated while performing layout after autosize (step 4).