Fixes deadlock caused by blocking Transport::Close()

I must say I am not sure why the block was there. What
the code did, it sent (as a job to another thread [1])
close request to the multiplexer and then blocked till
the multiplexer finished. As said, the code was probably
there to fix something, but it wasn't a correct fix
so if it breaks something I'll deal with it differently.
On first glance I didn't see a problem with removing it
since lifetime of the multiplexer is preserved using
a shared_pointer in the callback to the Multiplexer::Close()
metond, and the method doesn't seem to access anything
in this Transport object.

[1] Since there were only two threads active, we were
in one of them and the other one was blocked by our
mutex, the call to Multiplexer::Close was never
executed.
Close multiplexer directly in Transport::Close

Don't send it as an action to another thread.
Renames test: BEH_API_RandomSizeSetup -> FUNC_API_RandomSizeSetup

Because it needs to run longer to avoid false negatives.
Merge pull request #27 from inetic/MAID-237-transport-close-deadlock

Maid 237 transport close deadlock
Merge branch 'next' into MAID-183-cant-bind-on-bootstrap
Changes log levels from kWarning to kVerbose

Where appropriate
Removes usage of DebugId(...) on few places