Trim Spaces on username Field in Config
I just helped some friends debug their HomeKit setup on a raspberry pi. Spent about 30m debugging, when I noticed a trailing space in the username field. Removed the space, and everything worked! Felt like magic!! 

### Before
```
{
    "name": "Govee",
    "username": "REDACTED@gmail.com ",  <--- NOTE: Extra space right here
    "password": "REDACTED"
    "platform": "Govee"
}
```

### After
```
{
    "name": "Govee",
    "username": "REDACTED@gmail.com",
    "password": "REDACTED"
    "platform": "Govee"
}
```

## Proposed Change
A few ideas that would have made this easier: 
* Just trim whitespace -> would have avoided the error
* Present a warning in config UI to warn users of the potential error. 

My thought is to trim on their behalf. I suspect there's no use case for leading/trailing whitespace in the `username` field. BUT I don't know anything about Homebridge/HomeKit development, so just throwing some ideas out there. I trust the excellent homebridge-govee developers here :)  

## Logs
Here are the logs I was seeing that clued me in that it might be some auth issue. 

```
[21/01/2024, 16:58:24] Homebridge v1.7.0 (HAP v0.11.1) (Homebridge CD08) is running on port 51544.
[21/01/2024, 16:58:28] [Govee] [LAN] client enabled and found 0 device(s).
[21/01/2024, 16:58:28] [Govee] [HTTP] could not use existing access token as does not exist, this is normally not an issue.
[21/01/2024, 16:58:43] [Govee] [HTTP] disabling client as Cannot read properties of undefined (reading 'token') at default.login (file:///var/lib/homebridge/node_modules/homebridge-govee/lib/connection/http.js:74:40).
[21/01/2024, 16:58:43] [Govee] [AWS] disabling client as requires HTTP client.
[21/01/2024, 16:58:45] [Govee] [BLE] client enabled.
[21/01/2024, 16:58:45] [Govee] ***** Disabling plugin [v10.3.0]. *****
[21/01/2024, 16:58:45] [Govee] ***** No devices found to initialise. *****
```