Change bluetooth support to a supportable solution

[fossfreedom]

Current budgie-control-center version

1.4

Use-cases

Bluetooth via BCC utilises a now unmaintained GNOME library- libgnome-bluetooth-dev. Distros (for now Debian) have requested all apps using the library to swap to another solution. If we don't do anything, apps like BCC maybe removed in future from their distro. This will have a knock-on effect of removal of budgie-desktop itself.

This library provides two parts - one a GTK3 widget which is used to display the Bluetooth devices within the BCC bluetooth panel. The second part is the bluetooth code to connect the widget to various bluetooth operations. I don't think bluez is involved - maybe wrong here.

Proposal

1. The simplest solution is to add a compile time option to not depend on the library and hide the bluetooth panel. The obvious downside is that the end-user / distro needs to find another bluetooth related manager such as blueman
2. The second simplest solution is to switch BCC to support alternative bluetooth managers such as blueman - by virtue of having the ability to launch their settings/controlling application. In the case of blueman this would be /usr/bin/blueman-manager. Having a bluetooth panel with a button is straightforward or such a button could be tucked under another panel such as "Networks"
3. A third solution is to rip from libgnome-bluetooth-dev the widget code, integrate this in BCC and switch to the bluez API. Likely to be a sizeable project in itself - risk/reward balance case I'm not convinced with since BCC in its current incarnation is not part of the budgie v11 direction.

References

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059485