Various classes in cntrl/md-sal use hardcoded dependencies on OSGI/karaf

1)sal-distributed-datastore:
A)ActorSystemProviderImpl

• accepts a bundle context in the constructor to use the bundle's
  classloader for reading Akka configuration. Also creates
  a QuarantinedMonitorActor hard-coded to restart karaf (bundle_0:stop)
  B)EntityOwnerSelectionStrategyConfigReader
• deprecated, uses bundleContext to retrieve osgi config admin service,
  then reads and parses the eos strategy config
  C)DistributedDataStoreFactory
• accepts bundle context in factory method to create DatastoreContextConfigAdminOverlay
  D)DatastoreContextConfigAdminOverlay
• gets config admin service via bundle context to listen on datastore config changes

2)sal-binding-broker
A)BindingToNormalizedNodeCodecFactory

• registers a BindingToNormalizedNodeCodec instance as an osgi service. To quote jdoc:
  "* This method is called via blueprint to register a BindingToNormalizedNodeCodec instance with the OSGI

• service registry. This is done in code instead of directly via blueprint because the BindingToNormalizedNodeCodec
• instance must be advertised with the actual class for backwards compatibility with CSS modules and blueprint
• will try to create a proxy wrapper which is problematic with BindingToNormalizedNodeCodec because it's final
• and has final methods which can't be proxied."