Remove feature that starts bundles automatically on 'deploy' operation

Historically we attempt to start an OSGi bundle that gets deployed through the management interface. This however is error prone when a larger set of bundles is deployed and may lead to a deploym,ent ordering issue.

Now that we have OSGi runtime operations for start/stop in place bundles should only reach INSTALLED state when deployed through the management interface. An explicit start/stop operation should be required.