[BUG] IPInfo token and the Redis URL reach logs and telemetry events #80

Two secrets travel further than they need to.

IPInfo token. ipinfo_handler.py:147 puts it in the query string:

url = f"{base_url}?token={self.token}"

response.raise_for_status() on a non-2xx raises aiohttp.ClientResponseError,
whose str() embeds the full URL. That string is interpolated into the failure
log and into the geo_lookup_failed telemetry event reason
(ipinfo_handler.py:103, :215). Any 401, 403 or 429 from ipinfo.io writes the
token to the log — and a 401 is precisely what a rotated or mistyped token
produces, so the failure that reveals the secret is the common one.

IPInfo accepts Authorization: Bearer <token>, which keeps it out of the URL.
The error string should be reduced to host and status either way.

Redis URL. redis_handler.py:106,118 passes
redis_url=self.config.redis_url into the connect and reconnect telemetry
events. redis://:PASSWORD@host:6379 is the documented URL form, so on a
password-protected instance the credential goes to the agent on every connect
and every reconnect — that is, most often when Redis is flapping.

Strip userinfo before including it (urlunsplit with the netloc rewritten), or
send host and port only.

Found while re-checking a private audit against the current release. Verified on guard-core 3.13.0, CPython 3.14.