Config UI: make messengers configurable devices

[Maschga]

Replaces #25768
Ref #26782

🖼 visualize messaging section
📱 use device api
💱 dealing with different sources of truth: evcc.yaml, UI yaml or new UI
🧩 migration: split email-uri into host-, port-, user-, password-, from- and to-keys
🧩 migration: split ntfy-uri into host- and topics-keys
🧩 migration: add disable-key to each event
🔕 add toggle to enable or disable specific events
📋 add default title- and message-values to each not-predefined event in the browser's language
💪 use TypeScript

TODO:

• migration behavior (parallel to yaml, lock ui if yaml exists)
• add e2e tests
• test each service:
  • Pushover
  • Telegram
  • Email
  • Shout
  • Ntfy
  • Custom

Config UI card:

Events:

Messengers:

Add messenger:

Example: Ntfy:

\cc @naltatis

[andig]

@Maschga wie gesagt- du kannst gerne den PR forken und dann auf master zielen. Ist viel Einfacher für dich!

[Maschga]

@andig How can I update the Events object? Can this be done via api/state? With the move to devices, the messaging object is unfortunately empty.

"messaging": {
  "Events": null,
  "Services": null
},

[naltatis]

introduce expand/collapse transition. improves initial event overview (all disabled by default)

animation.webm

[naltatis]

Replace Name: db:xx tooltip on open button with [i] > dropdown. Better mobile support, more intuitive placement.