Fix AW3423DWF E_PIPE on init for newer firmware

My AW3423DWF Alienware RGB monitor on the latest firmware (M3B107) was ignoring OpenRGB commands. I wrote up a quick and dirty Python script to write bytes directly to the device the same way the OpenRGB controller does to debug, and was getting an E_PIPE error right off the bat on the init step.

Apparently, Alienware must have updated their firmware at some point to require the full 192-byte report for init. Sending the full 192 bytes worked for my script, and I made the same change to the controller code. My monitor responds as expected now with the patched binary.

Related to #3213 (closed)