fix: remove duplicate useEffect, console statements

[CK-7vn]

Description of the change

Frontend cleanup that takes care of duplicate React hooks, and console statements, also prettier did some stuff in there too on save..so..

• Related issues: https://app.asana.com/1/1201607307149189/project/1209460078641109/task/1212571858075650?focus=true
• https://app.asana.com/1/1201607307149189/project/1209460078641109/task/1212571424508064?focus=true
• https://app.asana.com/1/1201607307149189/project/1209460078641109/task/1212554680602728?focus=true

Additional context

• LoginForm.tsx: Removed a duplicate useEffect that was causing the countdown display logic to run twice on every lockedOutSeconds change. The first effect already handles the timer setup AND display formatting, so the second was redundant.
• FAQs.tsx: Cleaned up the analytics logging function - removed console statements and simplified to a fire-and-forget pattern since we don't need to handle analytics failures.
• LibraryViewer.tsx: Removed 3 console statements (debug log + error logs) from bookmark/favorite handlers. The toaster already provides user feedback for errors.
• BulkUploadModal.tsx: Removed 3 console.error statements from catch blocks. Same reasoning - toasters handle user-facing errors.

Removed the console statements because they can leak internal state and debugging info to users, the duplicate useEffect could cause race conditions, and changed the catch(error) to catch where the error variable wasn't being used, this will help avoid no-unused-vars lint.

[corypride]

Good Cleanup.

[carddev81]

Looks good! Nice clean up