Add ability to see the elapsed time of triggers with "for" timers in automations (ideally exposed as special timer sensors)

[ncd7]

Describe the feature

Automation triggers supports extremely useful "for" timers natively.
It is currently impossible to see the values of those timers in a dashboard.
While one possible solution is to imply create and manage your own helper timer, it would be vastly better from a user's perspective to enhance the existing native "for" conditions to expose their elapsed time.

I understand the difficulty in creating stable identifiers for those but that's solvable - e.g. automation name appended by the trigger condition id (so a requirement could be that triggers MUST have an ID and a "for" if you want to see its timer).

Those timers can be either read-only or could be controllable (eg resettable).

Use cases

I have two main use cases for me personally:

1. to be able to visualize how much is left on the timer on a Dashboard (eg a timer to "move" when you are sitting too long in a spot powered by a mmwave sensor; a fan timer in the a bathroom, etc)
2. to greatly enhance debuggability of automations with "for" triggers.

I am aware that most "for" triggers are short lived and for longer-lived the recommendation is to use explicitly defined custom timers because "for" triggers do not survive restarts. However, there is a wide "middle ground" set of "for" condition on the order of minutes, but not hours, that would be very clunky to have to create custom helper timers for since the native feature is so incredibly easy to use. The vast majority of my personal configuration uses timers on the order of 30 seconds - 10 mins and for those I'd love to be able to not have to manage custom timers.

(For anything over 1hr, I do use helper timers and that's fine).

Current workarounds

Use timer helpers. That is clunky and leads to A LOT of complexity as you need to handle the state of the timer (start/cancel/restart/etc). It's just super unideal and overcomplicates automations, hiding the underlying logic you are trying to implement in a ton of YAML boilerplate.
Moreover, 90%+ of the time I find myself having to resort to the manual timer is exactly because I want to be able to visualize the remaining time on a Dashboard. Other 10% is when timers are super long-lived (eg 2-3 hours) and I need to protect against restarts.

Anything else?

Thank you for creating the best home automation platform! <3