Improve documentation for 429 error
# Preface
## **_Please read... I promise this isn't just another 429 auth issue duplicate!!!_**

---

**Describe The Problem:**
There's clearly a ton of users posting about the 429 issue and I think part of the issue is the error that's displayed in the plugin and in the logs...

### Here's a summary of where my head is at and why I think there's an issue with the verbiage:
- A 429 error usually indicates that a client is exceeding a rate limit
- Exceeding a rate limit and **_continuing to make requests_** typically _**extends**_ the lockout
- Users may see constant failures being logged out and think that the 60-90 min. lockout is being `extended` after each request/failure

**To Reproduce:**
Trigger the 429 lockout and observe the error in the Homebridge logs or on the plugin's `Feature Options` tab

**Logs:**
```
myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
```

**Environment:**
* **Homebridge Version:** 1.6.1
* **Node Version:** 18
* **Homebridge-myQ Plugin Version**: 3.4.3
* **Operating System and OS Version:** Raspbian GNU/Linux Buster (10)

---

### Follow up Questions
- Will the lockout actually expire if the plugin is still spamming requests even though there's a 429?
- Does the user need to take any action or just wait? (I currently feel like maybe I need to just unplug my home bridge device for 90 mins...)
- Would it make sense to add a manual check to prevent constant failures after an initial 429?