Be more verbose for MQTT?
<!-- FEATURE REQUESTS THAT ARE NOT FILLED OUT COMPLETELY WILL BE CLOSED AUTOMATICALLY WITHOUT WARNING AND WILL NOT RECEIVE A RESPONSE. THE FORM IS HERE FOR A REASON. :). -->
<!-- Please ensure you read the documentation before creating a feature request to ensure the functionality doesn't already exist. -->

**Is your feature request related to a problem? Please describe:**
When having both normal motion zones and smart detection zones configured on a camera, [this line](https://github.com/hjdhjd/homebridge-unifi-protect/blob/main/src/protect-nvr-events.ts#L528) prevents MQTT events from being published for smart detections most of the time, as a normal motion event usually is already inflight when a smart detection happens.

The safeguards against spamming motion events that are likely caused by the same thing make perfect sense for HomeKit integration.

However, when using MQTT, I'm interested in every event. If I don't want both the motion and the smart detection event I either don't subscribe to both or filter them further down the line.

In my specific use case I want to turn on porch lights on smart detections of persons or vehicles. This prevents spiders in front of the camera from turning on the porch lights in the middle of the night, which is great. I still have motion zones configured on the same camera for other recording purposes, but those currently break the MQTT notifications for smart detections.

**Describe the solution you'd like:**
Publish MQTT events earlier, without consideration for potential duplicate events. 
In the "worst case", both motion and smart detection are set to true at the same time. Even though this is a behavior change, considering that smart detections currently only work properly if there are no normal motion zones configured, this change is unlikely to break existing setups. What do you think?

**Describe alternatives you've considered:**
Check Motion and Smart Detection events or duplicates separately. Same as above, it's not like you can use both right now. Although this might spam things on the HomeKit side, I'm not sure.

**Additional context:**
I'm only using the plugin for it's MQTT functionality. I don't have homebridge registered in HomeKit, but this doesn't seem to cause any issues or behavior change.

<!-- Click the "Preview" tab before you submit to ensure the formatting is correct. -->

Thank you for the plugin, it's already very useful 👍 