DeletedUser443 Reading around a bit, there are a bunch of articles from around 2018 claiming that various VPNs were not catching STUN traffic, thus WebRTC code in some browsers determined the public IP address. More recently I am seeing lots of WebRTC leak testers and lots of VPN providers warning potential customers that maybe unspecified competitors leak public IP addresses via WebRTC, but it's not clear it's actually still happening.
I think the thing to do would be to use a good VPN and, if desired, periodically run some leak tests. Note that WebRTC isn't limited to browsers; any app can run the protocol too (source). And even without WebRTC, any app could use STUN to determine an IP address -- or could roll its own equivalent protocol.
I think the solution to leaky VPN clients is to use a non-leaky VPN client.