This can be used by code that depends on policy to re-evaluate
choices they have made in the past that could now change based
on the new policy.

The core may be the last object holding a reference to the endpoint,
so the unregister call may destroy it.

This allows loading of config and modules when deployed in
the target system without setting environment variables.

and also implement
* global-added/removed signals
* a foreach function to iterate through globals
* registering modules and factories with the same key

g_weak_ref_clear destroys the weak ref, so it will crash
when _finalize() tries to destroy it again

This changes the registration point to be the endpoint and not the
session manager, as it seems easier to implement (the implementation
will not need to keep a pointer to the session manager around)

* Make streams a GVariant array, for future-proofness
* Add API for controls (volume, mute, brightness, contrast, etc...)
* Remove API for profiles (it's not well-thought; may be re-added
  in the future)

After discussing things at the AGL May 2019 F2F meeting
and reflecting on the initial design of WirePlumber,
it became clear that it needed a fresh start.

This reverts commit daa49af5.

Exposing a spa_dict is necessary to allow using native pipewire API
that deals with these properties.

The internal structure change avoids mem copies when we need to
return a spa_dict.

This commits also removes exposing internal info structures via the
properties mechanism. This needs more thinking...

This makes it more intuitive to get other attached interfaces
from the core

We are going to use this in other object types as well

* make the registries available as dynamic interfaces of the core
* improve a bit the C API of WpObject & WpInterfaceImpl

the GType cannot be in statically allocated data,
since it's not known at compile time