[REFACTOR] Fix linting errors

### 🔍 Description
We want to use linting to maintain code standards in the JavaScript code - there are several linting errors that need to be fixed.

### 🎯 Goals
- Improve code readability/maintainability.
- Improve adherence to best practices.

### 📌 Areas to Refactor
- Javascript files for the Electron Client

### 💡 Suggested Approach
Navigate to the interface folder for the Electron client.
```bash
cd src/interface
```
Run the lint script using npm.
```bash
npm run lint
```

This will show you certain errors that exist with linting in the JS codebase. Here is an example.


Resolve the errors. Also verify the eslint config and remove unnecessary checks (for example, TypeScript checks are not required since our codebase is in JavaScript)

### 📚 References
- Docs/Resources: [ESLint Docs](https://eslint.org/docs/latest/)

### ✅ Definition of Done
- [ ] Code is cleaner and more modular.
- The code passes the ESLint checks.
- No breaking changes introduced.

Inizia in src/interface ed esegui npm run lint per esaminare gli errori attuali di linting JavaScript. Ispeziona la configurazione di ESLint e i file del client Electron segnalati, quindi verifica che i controlli di linting vadano a buon fine senza Breaking Changes.

Scritto dal modello di indicizzazione a partire dal testo della issue.