io: Yield rather than wait when already in coroutine

io: Yield rather than wait when already in coroutine

The new qio_channel_{read,write}{,v}_all functions are documented
as yielding until data is available.  When used on a blocking
channel, this yield is done via qio_channel_wait() which spawns
a nested event loop under the hood (so it is that secondary loop
which yields as needed); but if we are already in a coroutine (at
which point QIO_CHANNEL_ERR_BLOCK is only possible if we are a
non-blocking channel), we want to yield the current coroutine
instead of spawning a nested event loop.

Signed-off-by: Eric Blake <[email protected]>
Message-Id: <20170905191114[email protected]>
Acked-by: Daniel P. Berrange <[email protected]>
[commit message updated]
Signed-off-by: Eric Blake <[email protected]>