TimeTracking: Prevent resolving issue without logging work

For timetracking to work effectively, the underlying data must be consistent. This means that developers have to log their work for timetracking reports to be meaningful.

Request: prevent resolving an issue if timetracking is enabled, work logged == 0 and resolution != duplicate, so developers are forced to log their work.