Possible notification race with tags

If a new commit is integrated into a repository branch and quickly tagged, the notifier may miss updating the "Resolved In Build" field in the issue associated with that commit. This happens if the same RepositoryWorkItem instance handles both the tag and the commit, because it will handle the tag first, before a suitable backport has been created.

This just happened in SKARA-1871 where I resolved it by forcing a re-evaluation of the tag.

I think the order of notifications need to be reordered, but we should probably investigate closer to see if there is a reason for the current ordering.