Event replacement API spans two classes

[KitsuneRal]

The API is spread across RoomMessageEvent and RoomEvent; the main reason for that seems to be that when the event is getting replaced, the data for the replacing event are put in unsigned and not in content JSON dictionary; but replacing an event with a non-message is not a good thing anyway. For now it makes sense to move isReplaced() and replacedBy() to RoomMessageEvent; and we'll see what MSC1849 will bring us.

MSC1849 was split in several other ones; the relevant one here is MSC2676 and it just landed in the spec. The way it's currently worded basically requires the replaced (and the replacing) event to be of m.room.message type. Rules out editing stickers (and replying to/with them), heh.