handle kanban wakeup fully

[ctengel]

took care of "asleep" with a31a32c - "someday" doesn't need a wakeup since strictly speaking asleep lists aren't invisible; the wakeup date just indicates when user should be notified that I am here.... someday is always here but never notified

so... typical workflow

1. create an asleep list for a given timerange
2. add/move tasks into that list
3. when wakeup date hits, user is notified somehow that a list is ready to wake up
4. user is continually notified as long as that list exists, has a past wakeup date, and has cards in it
5. typically user resolves it by merging that list into active backlog, which then will resolve it

for the "someday" case

1. user creates a someday list
2. add/move tasks to list
3. during usual org sessions, user moves stuff over
4. list never goes away

Originally posted by @ctengel in #93

essentially - notify the user!

[ctengel]

Part of #98 ?