Fix Google Places text search: switch to locationBias, add request/response logging

[Copilot]

Text search calls to Google Places API (New) were returning 400s due to locationRestriction + circle being invalid for :searchText — only :searchNearby supports that combination. This was silently dropping all text search results (e.g. cafe searches). Additionally, API call logging lacked request/response bodies, making debugging opaque.

Changes

• places/google.go: Switch googleSearch from locationRestriction to locationBias for :searchText. Capture and pass request/response body strings to RecordAPICall.
• app/apilog.go: Add RequestBody/ResponseBody fields to APILogEntry; extend RecordAPICall signature to accept them.
• weather/google.go: Update RecordAPICall callers to pass empty strings (GET, no body).
• admin/api_log.go: Render collapsible <details>/<summary> rows per log entry to expose request/response payloads inline.

// Before (invalid for :searchText — causes 400)
"locationRestriction": { "circle": { ... } }

// After (correct for :searchText)
"locationBias": { "circle": { ... } }

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.