fix(GODT-2442): Handle event poll not starting after resync

It is possible, on slower machines, that the new event poll task is not
yet registered and attempts to cancel have nothing to cancel.

In this case, we need the refresh event to cancel the task, at that
point it is guaranteed that the task exists.

internal/user/user.go

@@ -299,15 +299,19 @@ func (user *User) SetAddressMode(_ context.Context, mode vault.AddressMode) erro
 	}, user.eventLock, user.apiAddrsLock, user.updateChLock)
 }
 
-// BadEventAbort stops user to communicate. The resolution is either logout or resync.
-func (user *User) BadEventAbort() {
+// CancelSyncAndEventPoll stops the sync or event poll go-routine.
+func (user *User) CancelSyncAndEventPoll() {
 	user.syncAbort.Abort()
 	user.pollAbort.Abort()
 }
 
 // BadEventFeedbackResync sends user feedback whether should do message re-sync.
 func (user *User) BadEventFeedbackResync(ctx context.Context) {
-	if err := user.syncUserAddressesLabelsAndClearSync(ctx); err != nil {
+	user.CancelSyncAndEventPoll()
+
+	// We need to cancel the event poll later again as it is not guaranteed, due to timing, that we have a
+	// task to cancel.
+	if err := user.syncUserAddressesLabelsAndClearSync(ctx, true); err != nil {
 		user.log.WithError(err).Error("Bad event resync failed")
 	}
 }