Fix cobweb 0.03 false setback

[483378]

Fixes #2094
When horizontally colliding with a block that has a cobweb on top and jumping into that cobweb, players are constantly being setback to a single position without any alerts, making it difficult to leave the cobweb and even impossible to move through it. The teleport is prevented by using uncertaintyHandler.wasAffectedByStuckSpeed() to check if the player was touching a cobweb. This fixes the issue on 1.8.

[Axionize]

@483378 isn't this only an issue on 1.8? Why does the commit apply to all versions? Is there anything in newer versions you can reproduce that had issues with the old code?

[483378]

@483378 isn't this only an issue on 1.8? Why does the commit apply to all versions? Is there anything in newer versions you can reproduce that had issues with the old code?

I did test my change on 1.21.4, the entire codepath (positionless packet + ground status change) is not really reached that often (It didn't happen at all when walking around or in that cobweb situation) because of the change from 0.03 to 0.0002 in 1.18.2. From 1.9 up to 1.18.1 there is still one small setback in that cobweb situation before my changes, although players do not get stuck anymore. After my changes, that small setback is gone.

Should I PR a version check for this additional condition? Do you suggest only exempting this in 1.8 or all the way up to 1.18.1?

[Axionize]

@ManInMyVan thoughts? I'm not familiar enough with this part of the engine code to know for certain but my six sense is tingling there's a minor movement bypass hiding here.