Open-Meteo transport errors carry coordinates into the log

[prorochestvo]

internal/infrastructure/weather/openmeteo.go's attempt deliberately strips the query
string from the status-code error, with the reason written in the code: to keep latitude and
longitude out of the logs. The transport-failure branch alongside it does not. It wraps the
*url.Error returned by httpClient.Do, whose Error() embeds the full URL:

Get "https://api.open-meteo.com/v1/forecast?...&latitude=51.169392&longitude=71.449074...": dial tcp: i/o timeout

Every caller that prints that error with %v therefore logs the coordinates. There are now
three call sites: Forecast, Geocode (which additionally carries the search term), and
ForecastRange.

This is hygiene rather than a policy breach — city coordinates are pre-approved data under
the beacon-data-privacy skill, and the line carries no user identifier — but it defeats an
intent the code states out loud, and it defeats it in three places.

Direction: redact inside attempt's transport branch, rewriting (*url.Error).URL to
host plus path before wrapping, so every caller inherits the same guarantee the status-code
branch already gives.

Found by review of #127 (P3, pre-existing, out of that PR's scope).

[prorochestvo]

Fixed on alpha in the squash commit 51e380c from PR #137. GitHub honours Closes #N only
on the default branch, so closing by hand — the commit body on the branch said Closes, which
was wrong for a merge into alpha and did nothing.

redactURLError rebuilds the *url.Error with host and path only, so all three call sites —
Forecast and ForecastRange with coordinates, Geocode with the typed search term —
inherit the guarantee the status-code branch already gave. A URL that will not parse redacts
to the empty string rather than to itself.

Verified in both directions: a forecast and a geocode against a dead listener assert the
coordinates and the term are gone while the path survives, and both were confirmed to fail
with the redaction removed. Plus the non-*url.Error passthrough and the unparseable URL.

The beacon-data-privacy skill gains the general rule rather than the incident: an outbound
URL is a log field, and a new outbound client wraps its transport errors the same way.