WWW-authentication issue
**Describe the bug**
Unable to trigger lock on Dahua Door Panel. Homebridge log returns 401 error

**Expected behavior**
Trigger door lock

**To Reproduce**
Steps to reproduce the behavior:
See config.

**Version** (output of `npm list -g homebridge homebridge-http-switch`)
 - homebridge: Homebridge v1.6.0
 - homebridge-http-switch: 0.5.36

**Configuration**
```json
"accessory": "HTTP-SWITCH",
    "name": "panelrest",
    "method": "GET",
    "switchType": "stateless",
    "timeout": 1000,
    "debug": "true",
    "auth": {
        "username": "xxxxx",
        "password": "xxxxxxxx",
        "sendImmediately": "false"
    },
    "onUrl": "http://xxx.xx.x.xx/cgi-bin/accessControl.cgi?action=openDoor&channel=1&UserID=101&Type=Remote"
```
**Additional context**
See attached showing what Dahua API says about 401 authentication errors:-

"Video products support digest authentication, see RFC 2617 for detail. If the http request sent by client does not provide valid "Authorization" header information, video products would return HTTP status code 401 and some information for authentication, then client should calculate authentication information according RFC 2617, and sent request again with authentication information using “Authorization” header. Video products return the required resource only if authorization information correct.
For example:
1. When digest authentication fails, video products’s response is :
2. Then the client calculates the digest authorization using information like username, password, nonce, HTTP method and URI with MD5, and then sends it to server.When digest authentication fails, video products’s response is “401 Unauthorized” :"

<img width="941" alt="Screenshot 2023-03-29 at 14 55 35" src="https://user-images.githubusercontent.com/11877958/228562502-c1272ec9-d64e-4a4a-bc6d-c97476674b63.png">
