Handle iphb wait requests with 32 bit time ranges

With libiphb >= 1.2.0 client processes can request
* wakeups using 32 bit time
* aligning the wakeup when it happens, without causing resume

The availability of the above data can be determined from version
field in the wakeup request structure. It resides in the area that
was zero padded in the previous versions of libiphb.

[iphb] Handle iphb wait requests with 32bit time ranges. Contributes to JB#16116
Protect logging ring buffer against overruns

Overflowing the logging ring buffer caused some messages to be lost
and others to be emitted several times which could make the logs very
difficult to understand.

Now when the ring buffer gets full, logging is stopped. Once the logger
thread has cleared sufficient amount of messages from the ring buffer,
the number of lost messages is emitted and logging continues.

Also double the ring buffer size to make overruns less likely to occur.
Delay client wakeup processing after wakeups are added / changed

Processing client wakeups and rtc programming immediately after each
wakeup request caused excessive traversal of active client list and
difficulties in interpreting what is happening from the dsme logs.

Delaying the client wakeup processing by 200 ms allows handling of
multiple near simultaneous wakeup requests in one go, which makes it
much easier to see/debug what happens when one client adds several
new wakeup request or multiple clients send updated wakeup request
after synchronous wakeup.
Reduce and clarify debug logging done from the iphb module
Merge pull request #64 from spiiroin/32bit_iphb_ranges

Handle iphb wait requests with 32 bit time ranges