avoid defining min/max macros in public headers
avoid defining min/max macros in public headers

if clients #include <qi/atomic.hpp> and don't
call qi_sanitize_compile_flags(), then the macros will be defined for
them.

Note: a better solution would be to avoid #including Windows.h from a
public header.

Change-Id: I57961d8d5d0a3068dcdd3e17184ca53fbff4c218
Reviewed-on: http://gerrit.aldebaran.lan/80215
Reviewed-by: jlamotte <70353e7b0c7d18b7fc75605daf0ccba69fcd3222@aldebaran.com>
Tested-by: sbarthelemy <9c154f64c36738f8e44d945c231ac417d15bd66e@aldebaran.com>
Reviewed-by: sbarthelemy <9c154f64c36738f8e44d945c231ac417d15bd66e@aldebaran.com>

aldebaran/libqi,aldebaran/libqi,aldebaran/libqi