Rework how StepsCache responds to step updates to improve robustness

Calculating exact changes in a document can be extremely difficult to do properly, as such, StepsCache ideally will not rely on them.

In this new approach, modifications to the step cache only require the last known unmodified step. As iteration across the document occurs, damaged regions of the cache are repaired and updated, and dead nodes are removed from the system.

This improves the performance of local edits immensely, at the expense of "long jump" type operations (e.g., add text then move immediately to the document end).
Fixes issue #417

# TODO
* [x] fix https://github.com/kogmbh/WebODF/pull/421#issuecomment-36220894

# Performance
## 1000pages.odt
|   | 2d21389 (master) | PR |
|---|----------|-------|
| 6. Insert the letter 'A' (x100) | 2251 | 225 |
| 7. Remove characters (x100, backspace) | 2925 | 331 |
| 8. Move to document end (direct) | 13 | 7699 |
| 10. Insert the letter 'A' (x100) | 447 | 148 |
| 15. Remove characters (x100, backspace) | 912 | 631 |
| 18. Align the current selection 'justify' | 18048 | 4476 |

## 100pages.odt
|   | 2d21389 (master) | PR |
|---|----------|-------|
| 6. Insert the letter 'A' (x100) | 431 | 226 |
| 7. Remove characters (x100, backspace) | 425 | 207 |
| 8. Move to document end (direct) | 6 | 526 |
| 10. Insert the letter 'A' (x100) | 891 | 151 |
| 15. Remove characters (x100, backspace) | 629 | 804 |
| 18. Align the current selection 'justify' | 1724 | 489 |