fix(next): remove console.error from next auth functions (#12881)

### What?

Removes the console.error() statement when there is a login error.

### Why?

IMO, Libraries should not pollute the console with log statements in all
but the most exceptional cases. This prevents users of the library from
controlling what goes to standard out. For example, if I want to use
structured logging, this log line breaks it.

It would be a little better if this console.error() only executed on
unexpected errors, but it executes even when a user puts the wrong email
/ password, so it gets printed relatively frequently.

I think you can just remove the logging and let the user of this
function catch the error and log as they see fit.

---------

Co-authored-by: Jacob Fletcher <[email protected]>

Author: jcgsville

packages/next/src/auth/login.ts

@@ -81,7 +81,6 @@ export async function login({ collection, config, email, password, username }: L
 
     return result
   } catch (e) {
-    console.error('Login error:', e)
     throw new Error(`${e}`)
   }
 }

packages/next/src/auth/logout.ts

@@ -23,7 +23,6 @@ export async function logout({ config }: { config: any }) {
       return { message: 'User logged out successfully', success: true }
     }
   } catch (e) {
-    console.error('Logout error:', e)
     throw new Error(`${e}`)
   }
 }

packages/next/src/auth/refresh.ts

@@ -36,7 +36,6 @@ export async function refresh({ collection, config }: { collection: CollectionSl
 
     return { message: 'Token refreshed successfully', success: true }
   } catch (e) {
-    console.error('Refresh error:', e)
     throw new Error(`${e}`)
   }
 }