Startup ordering based on OSGi Capabilities

[nedtwigg]

So far we have been completely ignoring the OSGi Provide-Capability and Require-Capability mechanism. When we let Atomos start every bundle, we get errors because the lazy bundles start before the workbench is ready. If we start the bundles ourselves, we get "unmet capability" errors which we have so far silenced by doing this

equo-ide/solstice/src/main/java/dev/equo/solstice/BundleContextAtomos.java

Line 71 in c6d44c8

setHeader(atomos, Constants.REQUIRE_CAPABILITY, Collections.emptyList());

So in this PR, we are going to take OSGi capabilities into account for bundle start ordering. That should mean that we don't need to start org.apache.felix.scr explicitly anymore

equo-ide/solstice/src/main/java/dev/equo/ide/BuildPluginIdeMain.java

Lines 264 to 266 in c6d44c8

	solstice.start("org.apache.felix.scr");
	solstice.startAllWithLazy(false);
	solstice.start("org.eclipse.ui.ide.application");

I bet this is also what was going wrong in

• UIEventTopic isn't working #33

So we might be able to make Atomos actually optional after this PR. Certainly the pure-Solstice will work better by the time this is done.