cursor location reports are inverted

[dankamongmen]

Going back to the original 2014 releases, kmscon inverts the y and x parameters of its cursor location reports. See dankamongmen/notcurses#784 for more detail, and a method to detect this inversion at runtime. It would be good if kmscon just properly formed CPRs: https://vt100.net/docs/vt510-rm/CPR.html

I've got a fix against the old tree; I'll rebase it against yours and submit a PR, unless you've already fixed this

[Aetf]

This was fixed in the library Aetf/libtsm#2

[dankamongmen]

oustanding! glad to see that this project has picked up a qualified and motivated maintainer.