This counter is intended to detect possible authentication issues (e.g.,
incorrect key). Socket errors, typically some form of "internet connection not
available," should not count against that.

…ng cases.

The Polaris network now sends an RTCM 1029 text message in response to an
authentication failure or similar error. The client no longer receives 0 bytes
when an authentication token is rejected.

This change avoids misleading warnings when authentication is valid but position
is not supplied, etc. We now return POLARIS_CONNECTION_CLOSED when the
connection is closed without an authentication error, including if we do not
receive any data from the network, and only return POLARIS_FORBIDDEN if we
suspect an authentication issue.

The P1_SetAddress() does not currently support IPv6. This may change in the
future.

Otherwise, ASAN needs to be manually loaded via LD_PRELOAD.

… out."

We cannot remove these. Internally, polaris.c accesses them if POLARIS_USE_TLS
is enabled _when polaris.c is compiled_. But if the user application does not
set POLARIS_USE_TLS when they compile and instantiate PolarisContext_s, the
context they create will be smaller than polaris.c is expecting and will cause a
buffer overflow.

Without these, loss of internet connection could get treated as an unexpected
socket error, rather than a timeout, and Polaris_Run() might exit its while loop
and never reconnect.