[evolution-data-server] Calendar: Drop leftover GDataClientLogin reference in the gtasks backend

[Milan Crha <mcrha src gnome org>]

commit 39febe79a93ee5ca92b23b0e1b388e0d63053de1
Author: Milan Crha <mcrha redhat com>
Date:   Mon Jun 21 12:01:53 2021 +0200

    Calendar: Drop leftover GDataClientLogin reference in the gtasks backend
    
    It was not needed, due to the OAuth2 being always used here.

 src/calendar/backends/gtasks/e-cal-backend-gtasks.c | 10 +---------
 1 file changed, 1 insertion(+), 9 deletions(-)
---
diff --git a/src/calendar/backends/gtasks/e-cal-backend-gtasks.c 
b/src/calendar/backends/gtasks/e-cal-backend-gtasks.c
index d4ab00459..553705ba4 100644
--- a/src/calendar/backends/gtasks/e-cal-backend-gtasks.c
+++ b/src/calendar/backends/gtasks/e-cal-backend-gtasks.c
@@ -379,15 +379,7 @@ ecb_gtasks_request_authorization_locked (ECalBackendGTasks *cbgtasks,
                        G_BINDING_SYNC_CREATE);
        }
 
-       /* If we're using OAuth tokens, then as far as the backend
-        * is concerned it's always authorized.  The GDataAuthorizer
-        * will take care of everything in the background. */
-       if (!GDATA_IS_CLIENT_LOGIN_AUTHORIZER (cbgtasks->priv->authorizer))
-               return TRUE;
-
-       /* Otherwise it's up to us to obtain a login secret, but
-          there is currently no way to do it, thus simply fail. */
-       return FALSE;
+       return TRUE;
 }
 
 static gboolean