geoclue polls wpasupplicant SSID list too often, resulting in lag and packet loss

Steps to reproduce:

1. Install GNOME Weather, or GNOME Clocks, or basically anything that determines your location
2. In GNOME Control Center > Privacy, enable Location Services (note that I am unsure about this part; it may not even be necessary)
3. Open the application requesting your location
4. Do something latency-sensitive on WiFi, like SSH or ping

Hypothesis:

When an application requesting your location is running in the background and location services are enabled, it seems to tell geoclue to use NetworkManager's D-Bus API for letting wpasupplicant scan for surrounding networks very often. This causes lots of latency spikes and visible lag.

Typing characters in an SSH session is rather laggy, and running something as simple as mtr 192.168.1.1 will show that every ~20 seconds the latency is over 100ms and packet loss occurs, while it's normally around 1.5ms with no packet loss. There are probably lots of other issues caused by this as well.

When a WiFi adapter scans for SSID's, it has to switch channels, delaying or dropping traffic in the meanwhile. This is what causes the lag and packet loss.

On phones connected to LTE this may make sense, but on a laptop which uses WiFi as its active network, this is detrimental to the connection.

Changing /etc/geoclue/geoclue.conf to disable WiFi scanning, solves this problem:

[wifi] enable=false

Ubuntu 20.04's version of Geoclue (2.5.6) has the WiFi source enabled by default, which causes quite some problems.

Downstream Launchpad bug report can be found here: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1875172