Add "Sony PLAYSTATION(R)3 Controller" to DS3 name matching logic

[painnick]

Some clone PS3 wireless controllers are not being recognized correctly.

While these recently purchased clone controllers report their device name as "Sony PLAYSTATION(R)3 Controller", the system fails to retrieve their PID (Product ID) and VID (Vendor ID).

uni_bt_process_fsm: requesting name
--> HCI_EVENT_REMOTE_NAME_REQUEST_COMPLETE
Name: 'Sony PLAYSTATION(R)3 Controller'

As a result, the software treats these devices using a generic driver. However, since the actual data packets sent by the device follow the PS3 protocol, the controller does not function as expected.

-----------> sdp_query_start()
Starting SDP VID/PID query for A0:5A:5E:CA:BE:B9
Vendor ID: 0x0000 - Product ID: 0x0000

To handle cases where the Controller Type cannot be automatically determined (due to missing hardware IDs), I suggest adding a feature that allows users to manually configure or override the Report Parser. This would ensure that even clone devices with incomplete descriptor data can be mapped to the correct controller profile.

[painnick]

I've identified why certain clone PS3 controllers are not being correctly recognized as DualShock 3 devices. These clones use the device name "Sony PLAYSTATION(R)3 Controller" (including the "Sony " prefix), which currently fails the name matching check in the driver.

Because the name does not match, the system falls back to a generic driver. However, these devices still transmit data using the standard PS3 packet format, leading to incorrect behavior.

Please update the uni_hid_parser_ds3_does_name_match() function to include "Sony PLAYSTATION(R)3 Controller" in the supported names list.

By adding this string, these specific clone controllers will be correctly routed to the ds3 parser, ensuring full functionality.