SendDataMulticast with status Fail exposed as NoAck

[AlCalzone]

Discussed in #7194

^{Originally posted by @Botched1 September 26, 2024}
I'm using a ZST39 running 7.22.1 and see multicast commands fail somewhat regularly. If I repeatedly send multicast commands I can get it to give the error maybe 3 out of 10 times or so...

[...]

What I see in the logs when it fails:

2024-09-25 20:30:38.430 ERROR Z-WAVE-SERVER: The node did not acknowledge the command (ZW0204)
ZWaveError: The node did not acknowledge the command (ZW0204)
    at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:5816:23)
    at Driver.sendCommandInternal (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6014:28)
    at Driver.sendCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6124:29)
    at BinarySwitchCCAPI.set (/opt/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:142:24)
    at BinarySwitchCCAPI.<anonymous> (/opt/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:164:16)
    at VirtualNode.setValue (/opt/node_modules/zwave-js/src/lib/node/VirtualNode.ts:172:39)
    at MulticastGroupMessageHandler.handle (/opt/node_modules/@zwave-js/server/dist/lib/multicast_group/message_handler.js:19:50)
    at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist/lib/server.js:139:100)
    at WebSocket.<anonymous> (/opt/node_modules/@zwave-js/server/dist/lib/server.js:60:45)
    at WebSocket.emit (node:events:517:28)

[...]

Investigation of the driver logs indicates that this is a transmit status of Fail, not NoAck, so it should be exposed as such.