Feature/fresh status

> Reusing old cached state leads to a lot of problems (bad dependency
> resolving if things have changed, problems with backwards compatibility
> when service classes change, ...).
> The `restore_current_state` function now provides the guarantee that the
> restored state will never be older than x seconds (x=10minutes
> currently).

> This behaviour can be toggled with the `must_be_fresh` kwarg.
> The `info` command requires this, for example - we may render the
> cached state even if it is too old, it's just a visual thing and does no
> mutation.
I thought about configurable but don't see the use-case.
Displaying that the status is outdated is a good idea, but I'm not sure if it makes sense to differentiate between

 * Older than 20 secs (red outline)
 * Older than 600 secs (? outline, means needs to be re-fetched)

Do you think it makes sense to "unify" both constants? This way a non-green outline in the age would always mean that the status needs to be re-fetched.