[BUG] DS4 won't reconnect correctly or use vibration over bluetooth

### Pre-flight checklist

- [x] I have searched existing issues and this is not a duplicate.
- [x] I have read the [Contributing Guidelines](https://github.com/CachyOS/linux-cachyos/blob/master/CONTRIBUTING.md).
- [x] I have verified the issue is reproducible with the latest available CachyOS kernel.
- [x] I have tried to reproduce the issue on Arch Linux's `linux` kernel.

### Upstream / vanilla kernel check

I tested with a vanilla/upstream kernel and the issue ALSO reproduces there (upstream bug — please report upstream)

### Kernel variant

linux-cachyos-lts

### System information (cachyos-bugreport.sh)

```text
https://paste.cachyos.org/p/64c5c1d.log
```

### Manual system information (if cachyos-bugreport.sh is unavailable)

```text

```

### Bug description

In have this DS4 controller that i usually use with my PC, the controller pairs successfully at first but i am never able to reconnect it normally, i have to put it in pairing mode every time i try to connect it, it does not for get the device but it will fail to connect unless it is in pairing mode, if i try to turn it on and connect it normally is says connected for half a second then says connection failed, also with that aside the device when connected through Bluetooth is only recognized as hid device, i am using a USB Bluetooth dongle, here are some more info and troubleshooting i tried
Controller: DS4 (054C:09CC) over Bluetooth
cat /sys/class/input/js0/device/capabilities/ff returns 0 over BT, non-zero over USB
Works fine over USB, broken over Bluetooth.

### Steps to reproduce

1- try to connect the controller normally over Bluetooth
2- try to enable any vibration capabilities

### Expected behavior

for the device to connect correctly and read as DS4 with full functionality vibration

### Actual behavior

device fails to connect, unless in pairing mode, and when forced via pairing mode vibration does not work

### Logs / stack traces

```text

```

### Additional system information

_No response_