clipboard code should not compress in the UI thread, not assume zlib

[Antoine Martin]

Difficulty is that the clipboard knows nothing about compression feature availability, as it is not directly tied to a client connection, at least on the server. When a new client comes in, we just hand over the clipboard instance...

Also, it does not have access to the per-client encoding thread, which would be the ideal place for slotting the compression work...

[Antoine Martin]

Groundwork done in r7041, we no longer assume zlib.

Remains:

• on the server: compress using the self.damage_data_queue (which should be renamed as compression queue or something more generic), or using a wrapper telling the network encode layer to do it
• on the client: we don't have any work queues, so it will probably have to be done by the network layer

[Antoine Martin]

• server encodes from the 'encode' thread as of r7049 - which means that clipboard can no longer arrive before the screen updates that go with it
• client encodes from the 'format' network thread as of r7051

Some ugly code remains in compressed_wrapper calls, but that is now well isolated and can be dealt with later.