Fetch body is overwritten in ImapProtocol, with fix solution

[thin-k-design]

Describe the bug
Data is beeing overwritten when reading the response in ImapProtocol. This happens, when the imap server sends back two responses for one request command. Here is an example:

>> TAG14 UID FETCH 182835 (RFC822.TEXT)
<< * 2005 FETCH (UID 182835 RFC822.TEXT {645163}
<< --000000000000ae3e6805e9e1bece
<< Content-Type: multipart/alternative; boundary="000000000000ae3e6605e9e1becc"
<<
<< --000000000000ae3e6605e9e1becc
<< Content-Type: text/plain; charset="UTF-8"
<<
<< Testbody
<<
<< --000000000000ae3e6605e9e1becc
{{... rest of the message content ...}}
<< --000000000000ae3e6805e9e1bece-- FLAGS (\Seen))
<< * 2005 FETCH (UID 182835 FLAGS (\Seen))
<< TAG14 OK Success

First the content after * 2005 FETCH (UID 182835 RFC822.TEXT {645163} is beeing correctly parsed.
But the line * 2005 FETCH (UID 182835 FLAGS (\Seen)) is beeing parsed after the body and $data is beeing overwritten in:
Connection\Protocols\ImapProtocol::fetch() Line 616

            $data = "";

            // if we only want one item we return that one directly
            if (count($items) == 1) {
                if ($tokens[2][0] == $items[0]) {
                    $data = $tokens[2][1];
                } elseif ($uid && $tokens[2][2] == $items[0]) {
                    $data = $tokens[2][3];
                } else {
                ...

Should be changed in

            if (!isset($data)) {
                $data = "";
            }

            // if we only want one item we return that one directly
            if (count($items) == 1) {
                if ($tokens[2][0] == $items[0]) {
                    $data = $tokens[2][1];
                } elseif ($uid && $tokens[2][2] == $items[0]) {
                    $data = $tokens[2][3];
                } else {
                ...

[thin-k-design]

Has been fixed in #233