This is not part of the policy, it's something standalone that writes metadata

Needs to be disabled by default, since it's not built by default now

Handles SUSPEND and RESUME wpipc requests in order to set metadata that will
eventually unlink or re-link endpoints.

After all, we can just load multiple lua config files/directories
from a single .conf file and so have both styles available for the
user to choose at runtime

This configuration allows splitting wireplumber into multiple instances.
The "main" instance takes care of loading and managing devices
The "policy" instance does all the linking and implements endpoints
The "bluetooth" instance runs the bluetooth devices & nodes

Test with (in separate terminals):
./wp-uninstalled.sh -c config-split -- wireplumber -c main.conf
./wp-uninstalled.sh -c config-split -- wireplumber -c policy.conf
./wp-uninstalled.sh -c config-split -- wireplumber -c bluetooth.conf

This script takes links that are created by policy-endpoint-client
and activates only the ones that should be active based on role
priorities

Links between endpoints and device nodes are done externally in LUA

Links items with media role set to existing endpoints. The target of the
endpoints is also configured.

It is not needed as si-standard-link can be configured with port contexts

Because it is only meant to be used with audio nodes

Because it is only meant to be used with audio nodes

Add all that goes with it.

If 'move' is set to true, endpoints will be moved to the new target when the
metadata 'target.node' key is present. If 'follow' is set to true, endpoints
will be moved to the newly changed default device automatically.