SingleFeatureTest now fails if diag CLI command would have failed

SingleFeatureTest now fails if diag CLI command would have failed

This will help us detect a whole range of issues, notably any
blueprint related problems, much earlier in our development cycle than
we currently are.

The log contains details re. OSGi missing and available services.

NB: This change includes a (surprisingly long!) "black list" of features
known to be broken right now.  These ideally should all be fixed, and
the black list removed.

IMPL: The new bundles-test was introduced here because I ran into Pax
Exam related ClassNotFoundException, which I could not to resolve any
other way.  Basically, the problem is that the "probe" bundle which Pax
Exam creates on the fly includes the SingleFeatureTest class, and not
classes it references.  In other tests like IT this works, possibly
because Pax Exam somehow finds them in src/test/java; but not from
features-test.  (The currently existing utility classes next to
SingleFeatureTest in features-test probably only work because those run
outside the probe?)

This also did not help, because it's never called, because the
ClassNotFoundException happened earlier, on loading of the class
already:

import org.osgi.framework.Constants;

@ProbeBuilder
public TestProbeBuilder probeConfiguration(TestProbeBuilder probe) {
    LOG.info("probeConfiguration()");
    probe.setHeader(Constants.DYNAMICIMPORT_PACKAGE, "*");
    probe.setHeader(Constants.EXPORT_PACKAGE,
"org.opendaylight.odlparent.featuretest");
    probe.setHeader(IMPORT_PACKAGE,
"org.opendaylight.odlparent.featuretest");
    return probe;
}

Change-Id: I328e503703770aab539fdf1f0a7804ba676596ac
Signed-off-by: Michael Vorburger <vorburger@redhat.com>