V1.7.0-2

🚀 New Feature: Manual Semantic Location Mapping

This update introduces the ability to manually map semantic location names (e.g., "Living Room Speaker", "Near Kitchen Display") reported by Google without GPS data to fixed coordinates.

• The Problem: Google often reports only the name of a nearby device ("Semantic Name") but no GPS coordinates. Previously, this resulted in updates being ignored or caught by the Google Home spam filter.
• The Solution: A new "Semantic locations" menu has been added to the integration options. Users can now map recognized names (case-insensitive) to a specific latitude, longitude, and detection radius.
• Logic: When a report with a known name arrives, the integration injects the configured coordinates and marks the report as "trusted." This happens before the Google Home spam filter runs, ensuring these reports are processed reliably.
• Diagnostics: A new diagnostic sensor sensor.*_semantic_labels lists all observed semantic names to assist with configuration.

🐛 Bugfixes & Improvements

• Fixed FCM Registration Loop: The FcmPushClient supervisor now correctly detects fatal errors (401/404) during registration. It stops endless retry loops and prevents log flooding when credentials have become invalid.
• Coordinator Stability: Extensive refactoring in GoogleFindMyCoordinator improves the handling of subentries and the self-repair logic for the internal "Service Device" in the Device Registry.
• Deferred Initialization: Improved handling of "blocking imports" during setup to prevent warnings in the Home Assistant log.

📚 Documentation & Tools

• Added new guide docs/SEMANTIC_LOCATION_MAPPING.md.
• Added new script script/translation_key_check.py to verify missing translation keys.
• Updated translations (de, en, es, fr, it, pl, pt, pt-BR).