Towards strings-vs-bytearray correctness in libImap
Fix string-vs-bytearray in encode/decodeImapFolderName
Pretty straightforward string-vs-bytearray fixes
string-vs-bytearray

Yes, this changes the return value, but this particular part was only useful
when debugging anyway.
GenUrlAuthTask: switch to working with QByteArray
string-vs-bytearray: mostly trivial changes
Use QByteArray for various IMAP-related paths

Using QString doesn't really make sense in this context because the data we
operate on are absolutely not Unicode.

The change is rather intrusive, though, so I hope that I managed to catch all of
the instances where the drag-and-drop operated on QStrings. Maybe we should
switch to regular URLs here.
Fix building with QT_NO_CAST_FROM/TO_ASCII in libIMAP
Fix building with QT_NO_CAST_FROM/TO_ASCII in libDesktopGui
Fix building with QT_NO_CAST_FROM/TO_ASCII in libAbookAddressbook
Do not redefine QT_NO_CAST_FROM_ASCII
Enable QT_NO_CAST_FROM/TO_ASCII on targets which are clean