* Use a direction instead of a string prop id
* Emit default-endpoint-changed again
* Get rid of the useless virtual methods

+ rename FEATURE_CONTROLS to FEATURE_PROPS
+ add accessor for the standard spa_param_info (info->params)
+ hide the low-level params API that nobody uses

+ use a more correct naming scheme to match the one from Spa
+ remove the default video source, since we now use a different
 session for video

+ add the useful _find_proxy() method

+ enable the new log writer on the executables
+ enable structured logging in the tests

There are 3 kinds of WpProxy objects:
 * the ones that are created as a result of binding a global
   from the registry
 * the ones that are created as a result of calling into a remote
   factory (wp_node_new_from_factory, etc...)
 * the ones that are a local implementation of an object
   (WpImplNode, etc...) and are exported

Previously the object manager was only able to track the first kind.
With these changes we can now also have globals associated with
WpProxies that were created earlier (and caused the creation of the global).
This saves some resources and reduces round-trips (in case client
code wants to change properties of an object that is locally
implemented, it shouldn't need to do a round-trip through the server)

+ use the pw_proxy API to find the bound id instead
of relying on WpGlobal

This has the advantage that it works also for exported
objects and for objects that have been created by calling
into a remote factory (such as the link-factory), so we can
now know the global id of all proxies, not only the ones
that have been created by the registry.

Currently all it does is that it prints the properties
of all device nodes (Audio/Source & Audio/Sink), which
is useful for editing the configuration files