v2.7.4 - Native timer events from presets

This release fixes native Home Assistant timer.* entities not firing their standard events when started from the card's preset chips or custom picker.

🐛 Fixed

• timer.started / timer.finished now fire when you start a native timer from a preset or the custom picker. Previously the preset chips (and the custom duration picker) always created a local, browser-stored timer, even when the card was set up around a native timer.* entity. It looked like the timer started, but the real timer.* entity never moved, so no timer.started event was emitted and automations listening for it never ran. The tile's own inline start already worked; now the presets and picker behave the same way.
• The card starts the native timer through the timer.start service when the target is a timer.* entity, so all the standard timer events (started, finished, cancelled, paused) come through for automations.

🔧 Behavior

• The native timer is chosen from default_timer_entity if it points at a timer.*, otherwise from the single native timer.* entity configured on the card. If several native timers are configured, presets stay ambiguous and fall back to the previous local-timer behavior; start those from each timer's own tile.
• No configuration changes are required. Local, MQTT, helper, and Voice PE timers are unaffected.

---

Full Changelog: v2.7.3...v2.7.4