Problem: test_security_curve build fails with Windows targeting 8 or newer due to duplicate definition of htonll

Solution: use custom implementation only on older Windows versions

Solution: add API and ZMQ_EVENT_PIPES_STATS event which generates 2
values, one for the egress and one for the ingress pipes respectively.
Refactor the events code to be able to send multiple values.

Solution: refactor code and add extra frame with value count before the
values in v2

Solution: expect additional events

Solution: do it, as above 32 bytes they might be on the heap

Solution: check for the available version instead

This reverts commit ac19d5f4.

This partially reverts commit 19c6aa5c.

Solution: add test case run with cap_net_admin
Fixes #3397

Solution: define UNITY_SUPPORT_64 to force 64 bit support

Solution: make compilation conditional

Solution: add test case

Solution: increase size to 256

Solution: output as hex instead

Solution: add test cases

Solution: unlink the socket file first

Solution: define uint64_t if not available in the system headers and
remove inclusion of inttypes.h which does not exist and is already
conditionally included in zmq.h if required, do not use PRIx64

Solution: correctly set the ipv6 flag in the connecting socket

Solution: add test case using ipv6

Problem: no assertions for endpoint addresses on ZMQ_EVENT_MONITOR_STOPPED and ZMQ_EVENT_LISTENING events

Solution: added assertions

Solution: close test socket

Solution: added such assertions and extended test utilities

Solution: dereference the pointer to the array before accessing the
element

Solution: add first test case

Solution: move general monitoring test utilities to new testutil_monitoring

Solution: migrate to unity

Solution: assign result to address

Fixes #3376

Solution: remove documents and tests for ZMQ_THREAD_PRIORITY getter. It
never worked and can never work as it has the same value as a get-only
option ZMQ_SOCKET_LIMIT. It cannot be changed without breaking ABI.
Note that the setter works fine as ZMQ_SOCKET_LIMIT is get-only.

Solution: mostly false positives, but fix them

Solution: create manually the random IPC file to reuse

Solution: use wildcards or random directories to avoid races when
multiple users are running the same test on the same machine

Solution: use memcpy instead of doing pointer arithmetics with casting
and dereferencing to fix the error on sparc64

Solution: if a multi-part message cannot be delivered by a PUSH socket
because the pipe is broken mid-way, drop the rest of the frames so that
the atomicity property is not broken.

Solution: migrate to unity

Solution: migrate to unity

Solution: migrate to unity

Solution: migrate to unity

Solution: do it

Solution: do it