Update scheduled issue type label nudger to be selective of update events
We are seeing race conditions in the scheduled issue type label nudger caused by back to back label changes, which are often triggered by our reactive processors. These race conditions result in issues getting multiple nudger comments, such as gitlab-org/gitlab#371788 (closed).
Proposal:
Make this processor more selective which event to react to. Since we can tell if the change was made to update milestone, we can update the applicable?
method to take into account of whether milestone was changed, otherwise return false.