Pairing broken on macOS Ventura up to (including) macOS Tahoe

Continuation of issue #456 (I don't think I can reopen an issue unless I closed it myself? Sorry, I'm not too familiar with GitHub.)

Thank you for looking into it! It looks like that fixed the problem of detecting the wrong MacOS version (The [PAIRING OSX] No need to add entry for OS X before 10.7. message no longer appears), but unfortunately I still can't get my controller to pair. I suspect that it may have to do with the mac address of the controller being written to the com.apple.bluetooth.plist file in /Library/Preferences/ , is it possible that file it needs to be written to changed in recent MacOS versions? I'm thinking that because none of my other bluetooth devices are in that file, in fact, there's not much data there at all. Just a guess though, you would have a much better idea of what's causing the problem than I would.

One thing that I think is worth noting is the controller works well with the example scripts when it's plugged in over usb, the issue is just pairing over bluetooth.

Here is a video of me trying to pair the controller to my Mac, in case you notice anything strange there.

Log from terminal:

bryce@Bryces-Air build % sudo ./psmove pair
Password:
Connected controllers: 1
[PSMOVE WARNING] Magnetometer in 04:76:6e:0f:0a:18 not yet calibrated.
PSMove #1 connected via USB.
[PAIRING OSX] Detected: macOS 13.1
[PAIRING OSX] Entry for 04-76-6e-0f-0a-18 already present.
Pairing of #1 succeeded!
Controller address: 04:76:6e:0f:0a:18
Calibration data available and saved.
bryce@Bryces-Air build % 

Start by reproducing the failure with the psmove pair entry point on macOS Ventura or Tahoe, using the provided terminal log as the expected context. Inspect how pairing interacts with /Library/Preferences/com.apple.bluetooth.plist and compare it with the USB example scripts. Done means a controller pairs successfully over Bluetooth on the affected macOS versions while USB behavior remains working.