Add compat flag to treat NIF as Basic CC event

[AlCalzone]

This is a hack for some older devices which send a NIF on double tap. Our "standard" behavior is to expose those as Basic events on supporting devices. Adding a compat flag would allow us to map those.

Discussed in #6643

^{Originally posted by nmpu January 26, 2024}
I discovered that my non-Plus NuTone switches and dimmers will send ApplicationUpdateRequest on a double-tap. This must have been an undocumented feature for engineering or tech support. I'd like to make use of it to cycle through presets on my dimmers. It would also be useful on the switches. It's somewhat limited in that you can't distinguish between up and down and it also affects the load, It's only useful if you double-tap up while on or double-tap down while off.

The Z-Wave JS response is to send MultilevelSwitchCCGet. That's perfectly reasonable. Since I can't trigger directly on the ApplicationUpdateRequest, I watch for the MultilevelSwitchCCReport which will never arrive unsolicited. The only other time I see MultilevelSwitchCCReport is after MultilevelSwitchCCSet which I can anticipate. I already have all my dimmers templated due to HA rounding errors, so I know when an update will be sent. I'm pretty happy with what I've got now, but I have to use a 5-second guard time to ensure I'm seeing the double-tap and not some remnant of a set command. This is because the dimmer step parameters are not configurable and it can take a long time to ramp before the final report is sent. I also have this problem.

Here are my questions:

1. I would like to trigger HA directly off the ApplicationUpdateRequest. Is this too esoteric to ever be considered as a feature request?
2. If I were to make the changes myself, is this something that could be included in the mainstream code?