2026.02.0 - Entity ID Compliance, Registry Normalization, and Duplicate Event Hardening

Fixes for Release Notes (2026.02.0)

• Fixed issue #40: invalid manually assigned entity_id values in sensor and geo_location entities.
• Removed explicit self.entity_id = ... assignments and now rely on Home Assistant to generate entity IDs automatically.
• This ensures all entity IDs are valid/sluggified and prevents the deprecation warning that will become blocking in Home Assistant 2027.2.0.
• After updating, some entity IDs may appear normalized (for example, uppercase segments converted to lowercase).
• Improved geo-location region handling by using the public feed description field and normalizing it to avoid showing the Region name: prefix in entity attributes and friendly names.
• Added safer event ID extraction from feed external IDs, with fallback handling for unexpected ID formats.
• Hardened config entry option handling by using safe defaults when options are missing, preventing potential KeyError issues on older or partially migrated entries.
• Added edge-case safeguards for geo-location naming so entity names remain valid and readable even when some feed fields are missing.
• Improved coordinator entity lifecycle handling to reduce duplicate geo-location notifications after transient feed errors: removals are queued and applied only after successful feed updates, while temporary ERROR updates no longer trigger delete/recreate churn.
• Improved duplicate-creation protection by deduplicating on stable INGV event_id (instead of raw external_id) to avoid repeated entities/notifications when feed external IDs vary for the same event.
• Removed aggressive geo-location entity registry removals during reload/teardown to align with Home Assistant lifecycle handling and reduce _2/_3 entity churn when changing integration options.
• Added a single config-entry migration to version 2 to clean legacy geo_location entities without unique_id and normalize legacy suffixed entity IDs (_2, _3) when safe.
• Added idempotent geo-location registry normalization during setup and after the first successful feed update to reduce recurring _2/_3 suffixes after reloads or option changes.