Currently the `data-service-initialized` emitted in compass-connect emits the connecting dataservice to the appregistry. This event is listened to in a few places and the data-service is stored. However if it fails to connect, this data-service object is a risk because any actions on it may introduce errors or side effects.

This ticket involves either removing the `data-service-initialized` event, and just using the `data-service-connected` event if it works for the use cases of the `data-service-initialized` listeners, or we see if we can change where the `data-service-initialized` event is emitted so it only emits for successfully connected connections. If we go with this second approach we should also ensure any handlers don't need to be using the dataservice while it is still being connected to.