v1.5.6 in Production: add Doorbell node, rem Package

Hi all, hope this plugin is working out for you. I am pushing v1.5.6 with a doorbell node as well as removing the package flag.

Thanks to @shergenr for pushing me to adding this right about the time I got a G6 Entry (finally gave up on the G4 Doorbell ever coming back into stock).

Test it out and make sure nothing else broke, but I did validate Ring, Person, Face. Didn't validate, Motion as I don't have that set-up on the doorbell. The Ring flag is held for 3s to make sure its not missed visually in the easy-ui , a program will catch it on switch, but you may not want to rely on status.

I removed package from all the nodes as it is an alarm so currently out of scope as the api doesn't push it.

Although, I am thinking that we could use the webhook feature of Alarms to get around their exclusion from the api. It would require some fiddling as we would need to set up a common nomenclature for webhooks to talk to this plugin. Let me know the interest out there.

## 1.5.6

- Doorbell camera nodedef (``unifi_camera_doorbell``): classify G4 doorbells and G6 Entry when the public API omits ``isDoorbell`` (``hasPackageCamera``, hardware ``type``, G6 + entry naming)
- Doorbell ring (GV18): honor ring events when ``ring`` is not listed in ``smartDetectTypes``; pulse RING when the API sends only end-timestamp ring events; hold ring status 3 seconds before NORING so Status and programs are visible
- Remove package status (GV5) and PACKAGE/NOPACKAGE commands from all camera nodedefs; ignore package smart-detect events — the public Integration API rarely delivers them as usable status
- After updating: reinstall profile 1.5.6, run DISCOVER, and recreate doorbell/camera nodes if Package still appears on Status