fix: use specific 'token provided' match instead of broad 'token' in GitLab CLI error normalization

The previous check used lower.includes('token') which would match any error
containing the word 'token' (e.g. 'unexpected token' in JSON parse errors),
misclassifying them as authentication failures. Changed to 'token provided'
to match actual glab authentication errors like 'no token provided' and
'invalid token provided', consistent with how the GitHub CLI error handler
uses the specific 'no oauth token' phrase.

Author: cursoragent

apps/server/src/sourceControl/GitLabCli.ts

@@ -101,7 +101,7 @@ function normalizeGitLabCliError(operation: "execute" | "stdout", error: unknown
       lower.includes("authentication failed") ||
       lower.includes("not logged in") ||
       lower.includes("glab auth login") ||
-      lower.includes("token")
+      lower.includes("token provided")
     ) {
       return new GitLabCliError({
         operation,