Fix response handling in TagModifyJob

I wasn't able to reproduce locally, but on CI we were hitting the
newly added assert when receiving response after the job said it
does not expect any more response.

The server will send either one FetchTags or one DeleteTag response
followed by ModifyTags response.