- What I did

• standardize timeouts for log reads and writes for logger adapter tests
• use an assertion framework in logger adapter tests

- How I did it
took the timeouts in all other logging adapter tests (10 seconds) as a benchmark for upper-bounds on what should be consider a failure on timeouts. 10ms for log reads is too short unless we consider that a performance test (e.g. the contract is that the daemon is in error unless it is able to serve logs in less than that). This should make builds on node azure-windows-rs1-5 more stable.

- How to verify it
go test

- Description for the changelog
standardized timeouts in logging adapter tests, and refactored with an assertion framework

- A picture of a cute animal (not mandatory but encouraged)