Fix timer blueprint target resolution for service events

[f3rs3n]

Fix timer blueprint target resolution for service events

Summary

call_service events keep service parameters under event.data.service_data, while timer and UI events expose entity_id at the event-data level. The blueprint currently assumes every non-conversation trigger has a top-level entity_id, so service calls such as set_timer(device_id=...) and cancel_timer(timer_id=...) can fail during initial variable evaluation.

This change:

• preserves conversation-device resolution through view_assist_entity;
• resolves service-call device_id through view_assist_entity;
• falls back to a top-level event entity_id;
• returns an empty target when the event has no device or entity;
• bumps the blueprint to 1.3.3 and adds the matching wiki changelog entry.

The empty fallback intentionally allows timer-ID-only cancellation to reach its existing global cleanup branch. It does not infer a satellite from the timer ID.

Validation completed

• exact resolver matrix: 8/8 using Jinja with strict undefined values;
• the same 8/8 matrix rendered through Home Assistant Core's real template API;
• the exact candidate blueprint was copied to an unused blueprint path, matched by SHA-256, and passed ha core check; the temporary copy was then removed;
• live set_timer(device_id=A) created the timer and status icon on satellite A and triggered the automation without UndefinedError;
• live cancel_timer(timer_id=...) removed the timer, cleared its icon, and completed the global cleanup branch;
• YAML parsed with Home Assistant's !input tags accounted for;
• CRLF-only line endings and the final CRLF are preserved;
• the diff is limited to two files and three intentional hunks;
• the Docusaurus wiki production build succeeds.

Test-boundary note

The available deployment has one View Assist satellite. Isolation and precedence were therefore tested with real satellite A plus a synthetic entity B in the Home Assistant template matrix. Warning, expiry, Snooze, and Dismiss belong to unchanged branches outside this resolver-specific gate; they are not claimed as tested here.

Scope and known limits

This change does not modify translations, Italian responses, sentence lists, integration code, or other automation branches. It also does not add end-to-end support for set_timer calls that provide only entity_id or no target: the existing set_timer_trigger branch still reads service_data.device_id when retrieving timers. Those forms remain documented limits, not positive acceptance cases.

AI assistance disclosure: AI tools assisted with research and drafting. I reviewed the complete diff and personally verified the tests and behavior described above.