Security: Remove sensitive data logging from console output

## Security Issue: Sensitive Data Logging

### Problem
The application logs sensitive information like API keys, authentication tokens, and user credentials to the console, which poses a security risk.

### Affected Files
- `src/renderer/settings.js` - Lines 591, 777: Logs API key operations
- `src/services/AuthService.js.backup` - Lines 116, 142: Logs email addresses during password reset
- `src/main.js` - Lines 1074, 1140: Logs authentication tokens from deep links

### Security Risk
- Console logs may be accessible to other applications or users
- Sensitive data could be exposed in development environments
- Violates security best practices for handling credentials

### Expected Behavior
- Remove all console.log statements that contain sensitive data
- Replace with generic success/failure messages
- Maintain debugging capability without exposing sensitive information

### Proposed Solution
1. Remove or sanitize console.log statements containing:
- API keys
- Authentication tokens
- User email addresses
- Password reset codes
- Any other sensitive user data

2. Replace with generic logging that indicates operation success/failure without exposing data

### Impact
- Improves application security
- Maintains functionality
- Follows security best practices
- Reduces risk of credential exposure

This is a good first issue for Hacktoberfest contributors to learn about security best practices in Electron applications.

Inspect the listed console.log statements in src/renderer/settings.js, src/services/AuthService.js.backup, and src/main.js, then search those files for other sensitive values being logged. Replace exposed API keys, tokens, email addresses, credentials, and reset codes with generic success or failure messages. Done means the affected operations still work without sensitive data appearing in console output.

Written by the indexing model from the issue text.