Light strips stopped working reliably after recent update
<!-- PLEASE READ BEFORE POSTING A NEW ISSUE
   → Please use this template as well as you can.
   → Things that may seem unimportant are often helpful in finding the cause of the issue.
-->

### What issue do you have? Please be as thorough and explicit as possible.

A recent update seems to have messed up the reliability of bluetooth enabled light strips. Not sure if related, but everything seemed to work flawlessly before the update that called for an update of Node from 14.x to 16.x. I first reported some of these issues around the time that update was published (https://github.com/bwp91/homebridge-govee/issues/167#issue-1088038195
). 

An update was pushed that resolved the errors being displayed in the log, and functionality seemed to be restored. However, none of my light strips have worked reliably since. They seem to work for a bit after a fresh reboot of homebridge, but eventually they stop responding to commands from homekit and I see the following error in the log:

```
[18/01/2022, 19:20:29] [Govee] [Living Room] could not be updated as BLE took too long at BluetoothLED.updateDevice (/usr/local/lib/node_modules/homebridge-govee/lib/connection/ble.js:165:15).
[18/01/2022, 19:20:29] [Govee] [Living Room] could not be updated as BLE took too long at BluetoothLED.updateDevice (/usr/local/lib/node_modules/homebridge-govee/lib/connection/ble.js:165:15).
[18/01/2022, 19:20:29] [Govee] [Living Room] could not be updated as BLE took too long at BluetoothLED.updateDevice (/usr/local/lib/node_modules/homebridge-govee/lib/connection/ble.js:165:15).
```

All devices continue to work through the Govee app.

### Details of your setup.
* Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS? 

Homebridge UI

* Which version of Homebridge/HOOBS do you have?

Latest version

* Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Raspberry Pi - Node.js Version | v16.13.2

<br class="Apple-interchange-newline">

* Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?

homebridge-govee v4.27.0. The last time the plugin worked reliably (for me) was in the version before the update came out that required me to update node.

* Which Govee devices do you have that are causing issues? Please include product models if applicable.

H6179
H6138
H613D

### Please paste any relevant logs below.
<!-- ABOUT LOGS
   → More logging can enabled with 'Debug Logging' in the plugin settings.
   → If you are posting an error then it is helpful for me to also see
     the previous few lines as this can show the cause of the error.
   → Please enter the logs between the two ``` lines below so that the
     logs are formatted in a way which is easier to read.
-->

```
[18/01/2022, 19:43:05] [Govee] [Living Room] not sending AWS update as not available or enabled.
[18/01/2022, 19:43:05] [Govee] [noble] scanning started.
[18/01/2022, 19:43:06] [Govee] [noble] found device [7c:a6:b0:5c:1f:fc] [GBK_H613D_1FFC].
[18/01/2022, 19:43:06] [Govee] [noble] found device [a4:c1:38:b4:bb:4f] [ihoment_H6138_BB4F].
[18/01/2022, 19:43:06] [Govee] [noble] scanning stopped.
[18/01/2022, 19:43:06] [Govee] [Living Room] has been reported [discoverable] via BLE.
[18/01/2022, 19:43:08] [Govee] [noble] scanning started.
[18/01/2022, 19:43:08] [Govee] [noble] found device [40:cb:c0:da:6f:ae] [undefined].
[18/01/2022, 19:43:08] [Govee] [noble] found device [15:83:a8:ca:67:aa] [undefined].
[18/01/2022, 19:43:08] [Govee] [noble] found device [a4:c1:38:a4:e5:88] [ihoment_H6179_E588].
[18/01/2022, 19:43:08] [Govee] [noble] found device [5a:41:13:bb:b1:52] [undefined].
[18/01/2022, 19:43:08] [Govee] [noble] found device [7b:79:52:26:76:24] [undefined].
[18/01/2022, 19:43:08] [Govee] [noble] found device [d0:03:4b:3a:33:10] [undefined].
[18/01/2022, 19:43:08] [Govee] [noble] found device [01:03:aa:00:09:18] [APM-0918].
[18/01/2022, 19:43:08] [Govee] [noble] found device [a4:c1:38:b4:bb:4f] [ihoment_H6138_BB4F].
[18/01/2022, 19:43:08] [Govee] [noble] found device [17:6e:5a:69:89:9f] [undefined].
[18/01/2022, 19:43:08] [Govee] [noble] scanning stopped.
[18/01/2022, 19:43:08] [Govee] [Living Room] has been reported [discoverable] via BLE.
[18/01/2022, 19:43:11] [Govee] [noble] scanning started.
[18/01/2022, 19:43:11] [Govee] [noble] found device [a4:c1:38:a4:e5:88] [ihoment_H6179_E588].
[18/01/2022, 19:43:11] [Govee] [noble] found device [7c:a6:b0:5c:1f:fc] [GBK_H613D_1FFC].
[18/01/2022, 19:43:11] [Govee] [noble] found device [d0:03:4b:3a:33:10] [undefined].
[18/01/2022, 19:43:11] [Govee] [noble] found device [a4:c1:38:b4:bb:4f] [ihoment_H6138_BB4F].
[18/01/2022, 19:43:11] [Govee] [noble] scanning stopped.
[18/01/2022, 19:43:11] [Govee] [Living Room] has been reported [discoverable] via BLE.
[18/01/2022, 19:43:13] [Govee] [Living Room] could not be updated as BLE took too long at BluetoothLED.updateDevice (/usr/local/lib/node_modules/homebridge-govee/lib/connection/ble.js:165:15).
```
