Include S0 plaintext in debug logs when NODE_ENV=development

[AlCalzone]

Discussed in #7157

^{Originally posted by @spudwebb September 12, 2024}
Is there an easy way to decode the serial data that one can see in the log file at debug level, when the node use S0 or S2?

Context: I'm investigating an issue with a lock (Kwikset 910) that is sending a door lock logging report with an "empty" status. Since it is marked as empty zwavejs does not parse any other information from the message sent. I suspect this lock to send a valid report in which only the status is wrong, because the same device was working with another driver. So, I would like to confirm this by manually parsing the message to check what data (timestamp, event type, user code) it contains.

2024-09-12T14:35:21.667Z SERIAL « 0x012f00a8000001004c2198810452043a03a036e03c87addd9941566e85b4ee9e7 (49 bytes)
                                  cfe98cc8ffbb27a074c3100b2007f7fd8
2024-09-12T14:35:21.668Z SERIAL » [ACK]                                                                   (0x06)
2024-09-12T14:35:21.671Z DRIVER « [Node 076] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -78 dBm
                                  └─[SecurityCCCommandEncapsulation]
                                    │ sequenced: false
                                    └─[DoorLockLoggingCCRecordReport]
                                        record #: 6 (empty)
```</div>