New issue by mayhair on void-packages repository

https://github.com/void-linux/void-packages/issues/46080

Description:
<!--
  if you are creating a bug report or package request, please fill out one of the forms here:
  https://github.com/void-linux/void-packages/issues/new/choose

  Don't request an update of a package, We have a script for that:
  https://repo-default.voidlinux.org/void-updates/void-updates.txt
  However, a quality pull request may help.
-->
There are two packages: `libopenaptx` and `libfreeaptx`, which allow the usage of the AptX audio codec for Bluetooth earbuds. The state of affairs is that `bluez-alsa` requires `libopenaptx`, while `libspa-bluetooth` (a part of the PipeWire project) requires `libfreeaptx`. However, both projects are virtually the same, so they can act as drop-in replacements for each other (presumably). `libfreeaptx` is a fork of `libopenaptx` which was made because `libopenaptx`'s author disallowed organisations such as FreeDesktop to contribute, believing them to violate the GPL licence. `libfreeaptx` is now preferred by the PipeWire project due to these lesser restrictions.

Is it possible that `bluez-alsa` can be configured to use `libfreeaptx` too, thus obsoleting the `libopenaptx` package?