- This feature stems from the single device age
- Depends on deprecated Privacy Lists (XEP-0016)
- No support in other clients makes it in the current multiple device world useless
- Hard to maintain, prevents us to use even basic features like MUC because it would leak presence

Check if encryption is activated for a JID before sending the message

This fixes an regression from the send message refactor

This allows for much faster access than with a list

Otherwise this becomes a bottleneck if we load many MUCs, e.g. StartChat dialog

There are times for example when we open the StartChat Dialog, where
we need potentially hundreads of DiscoInfo entrys instantly.

If we execute a database query for each one of them this becomes a
bottleneck

- light refactoring of code which uses the service jid

- Move stanza building and message logging code into message module
- Don't use event flow to create and send messages
- Remove resource lock
- Properly support sending a message to multiple recipients

A roster push contains always the whole entry, so instead of updating
only the attributes which are present in the roster push, fill all missing
attrs with default values, e.g. None for a missing name attr

Fixes #9963

This method is called by the MessageWindow on the
currently active control, when it gains focus.

This allows the controls to decide by themself what should be focused
inside the control.

For example the GroupchatControl could have the change nickname page
open and would want to focus the nickname entry

closes #9961

- Change default timestamp to include date

closes #9272

The Client instance is now always the first argument

- xesam:artist is always a list of strings rather than a single string
- Moved the parsing logic into MusicTrackInfo

Reinstall python packages inside the virtualenv to have more control on versions