Refactor Room::setState()

There are two important aspects here:
- Introducing Room::setState(evtType, stateKey, contentJson). These
  components are ultimately what is getting sent to the homeserver,
  so it makes sense to expose a respective `setState()` overload.
  Unlike setState(event) the new overload can be Q_INVOKABLE.
- Room::setState() is no more const. Although it doesn't cause any
  changes in Room class (and only transient changes in Room::Private),
  it ultimately initiates a change in the room state, so calling it
  const has always been a bit of hypocrisy. If you relied on that, you
  most likely do something wrong (see the fix to User::rename()
  in this very commit for a simple example of such wrongness).

Also: the backend is simplified by calling the original templated
Room::setState() instead of calling Room::Private::requestSetState()
that does exactly the same thing.

0 files changed, 0 insertions, 0 deletions