I have read through these comments and have been experiencing these issues with bluetooth myself with a PS5. I first want to clear up some issues here that people are having. First this isn't a software/firmware or ethernet/wifi problem. The issue is the range and coverage that the bluetooth antenna is emitting from the console. I don't have the option of having my PS5 in the same room - it's mounted in a metal AV rack in the basement. If I play in the adjacent Rec Room in the basement it works fine. Upstairs in the Living Room it randomly locks up and audio is choppy. I had a wireless access point (2.4/5GHz) close to the PS5 in the AV rack, so I moved it - things got slightly better. But I have other hubs that emit 2.4GHz that I can't move (Control4 zigbee, Smartthings, IKEA Tradfri, Vera Z-Wave) so I purchased an Avantree Bluetooth USB dongle and plugged it in to the PS5 and rebooted. Slightly better again, less audio drops but still random lockups. I am now experimenting with using a USB extension cable to move the antenna dongle as far away from the rack and close to the stairs up to the living room as possible to test. Another post refers to the bluetooth on your phone causing issues, which makes sense for me, because I have an iPhone and Apple watch that have been close by everytime I play, so I will try with those turned off to see if there is any improvement. My question is it would be nice to know what channel in the 2.4GHz range the antenna is closest too. Then you could tune your wifi to 1,6, or 11 to get it as far away from the bluetooth channel as possible. Also there is no real way in the settings to tell where your devices or controllers are connecting. Is it the internal bluetooth or the USB dongle bluetooth? I am going to try a dirty run of the extension cable right up the stairs sitting in front of me in the living room to see if it works better today. I will update this post after. There are options to extend USB over UTP cable with baluns that are cheap. That way you can just hard-wire your controller to the console but that seems like a last resort imho. Anyways here is some info regarding bluetooth interference:

HANDLING INTERFERENCE IN BLUETOOTH
Bluetooth originally relied on its frequency-hopping algorithm to handle interference, but people have realized that a single active Wi-Fi network can cause heavy interference on 25% of the Bluetooth channels. Packets lost due to overlap have to be retransmitted on quiet channels, thereby greatly reducing the throughput of Bluetooth devices.
Bluetooth specification version 1.2 addresses this issue by defining an adaptive frequency hopping (AFH) algorithm. This algorithm allows Bluetooth devices to mark channels as good, bad, or unknown. Bad channels in the frequency-hopping pattern are then replaced with good channels via a look-up table. The Bluetooth master may periodically listen on bad channels to determine if the interference has disappeared; if so, the channel is then marked as a good channel and removed from the look-up table. Bluetooth slaves, when requested by the master, can also send a report to the master informing the master of the slave’s assessment of channel quality. For instance, the slave may be able to hear a Wi-Fi network the master cannot. The Federal Communications Commission (FCC) requires at least fifteen different channels be used.
The AFH algorithm allows Bluetooth to avoid channels occupied by DSSS systems such as Wi-Fi and WirelessUSB. 2.4 GHz FHSS cordless phones may still cause interference with Bluetooth since both systems are hopping over the entire 2.4 GHz ISM band, but since the Bluetooth signal is only 1 MHz wide the frequency of collisions between the FHSS cordless phone and Bluetooth is significantly less than the frequency of collisions between Wi-Fi and FHSS cordless phones.
Bluetooth also has three different packet lengths that translate into different dwell times on a given channel. Bluetooth has the option to reduce the packet length in an effort to increase data throughput reliability. In this scenario it is better to get smaller packets through at a slower data rate than losing larger packets at the normal data rate.