listen_state should take into account entity's last_changed for immediate triggers

[Ten0]

Is there an existing feature request for this?

• I have searched the existing issues

Your feature request

Currently, for immediate listen_states, AppDaemon will wait at least the specified duration after AppDaemon's start (or trigger creation) before running the trigger, even if we can know that we can actually wait for less time and still be sure that the state we are listening for has not changed for longer than that time.

To solve this, when registering a listen_state, we could look at entity's last_changed that comes back from HomeAssistant's API when choosing how long to actually wait for.
This would make such triggers survive AppDaemon reboots/reloads much better, as it would mean that such triggers could typically recover their "I've already waited for this long" state.