Fix SDNC service registration

Fix SDNC service registration

Instead of registgering services via BundleActivator(s), use blueprint
instead.  This change deletes the RecordingActivator, as it was just
used to kickstart the service registration using felix dm.  The idea
here is to instead use blueprint through recording-blueprint.xml.

The decision was also made to register the Service(s) using the
implementation class name instead of the interface class name for
backwards compatibility reasons.  In all reality, registering Service(s)
under the implementation name is less future proof since clients are
no longer able to easily swap in a separate implementation Service.
In the future, we should consider finding usages of this Service and
ensuring that they poll for the interface rather than the implementation.
However, that is separate from this change and is considered future work.

Issue-Id: SDNC-54
Change-Id: I757bb90f91d114668c153ec5debb5c65af44452a
Signed-off-by: Ryan Goulding <ryandgoulding@gmail.com>