Add support for persisting Sting/Dagger created arez components

[realityforge]

The current infrastructure requires that the user explicitly construct the sidecar when the peer is created but this is not viable when sting/dagger is responsible for creating the arez components. We should investigate how to enable this if/when the demand arises.

This will likely also required the explicit provision of ids as described in #2 as sting/dagger created arez components are typically services that have no user controllable component id (and may generate an error in a future version if we try to add an id).