This might be the simplest and weirdest fix of all time.

Again, the core issue is that when we receive batched change params, the ranges are always relative to the original state. This is why we offset them after each. While this is required for our statement range logic to work, it breaks the change tracking for changes to the text. Here, we need to use the un-adjusted range.

So yeah, all in all this needs a serious refactor at some point :D

had to update two tests because turns out their data was wrong - the new one is freshly taken from VSCode (neovim never sends batched changes).