Clean up OdtDocument cursor position tests

Make OdtDocument cursor position tests more granular in how they are reported. This makes it easier to troubleshoot individual failing tests as the individual test is more specific.

* Extend core test runner to cope with test names containing angle brackets
* Verify the number of steps vs. expected number of cursor positions
* Remove doc length check for non-changing variables
* Report one test per cursor position document fragment
Still slightly confused why only `<` is cared for and not also `>` (and perhaps `&` for a possible test name char)? Because browsers can do proper error resolving with those other entities (no `<` before -> show `<` as char, no entity name after & -> show as char)?