[Launcher] Add dependency to default component provider

Additional case of #199 occurs when DefaultComponentProvider is null during first MCT launch. Adding this as a reference for LaunchMCTService in `OSGI-INF/service.xml` ensures that one is available before trying to launch MCT. (DefaultComponentProvider comes from a separate bundle, mctCoreTaxonomyProvider)

Since bind/unbind are no-ops (references are just used to declare dependencies; specific objects are obtained through Platform) change method signature to object, so they can both be reused in service declaration