Improve error handling and logging

[MartinPTielemans]

Description

The application currently uses basic console logging (eprintln!, println!) and lacks comprehensive error handling in several areas.

Current issues:

Frontend

• No error boundaries for React components
• Limited error feedback to users
• Console errors without proper handling

Backend

• Basic eprintln! logging instead of proper logging framework
• Missing error handling in clipboard operations
• No structured logging for debugging

Code examples:

// In main.rs - basic error logging
eprintln!("Failed to check for updates: {}", e);

// In command.rs - swallowed errors
eprintln!("Failed to update clipboard with translated text: {}. Error: {}", translated.clone(), e);

Proposed improvements:

1. Add proper logging framework (e.g., tracing or log crate)
2. Implement error boundaries in React components
3. Add user-friendly error notifications in the UI
4. Structured error handling with proper error types
5. Add retry mechanisms for clipboard operations
6. Log rotation and configuration for production use

Benefits:

• Better debugging capabilities
• Improved user experience with clear error messages
• Production-ready logging for troubleshooting
• More robust application behavior