Test lazy-loading when there are no candidates

It should decide that `intf` is instantiated even though (a) it doesn't
see a constructor for it and (b) it is an interface. It isn't ideal
instantiating an interface, but it stands in for a class which
implements the interface.

Author: Owen Jones

regression/cbmc-java/lazyloading_no_candidates/Test$factory_intf.class

@@ -0,0 +1,12 @@
+public class Test {
+
+  interface factory_intf {
+    public intf getintf();
+  }
+
+  interface intf {
+    public void f();
+  }
+
+  public static void main(factory_intf i) { i.getintf().f(); }
+}

regression/cbmc-java/lazyloading_no_candidates/Test$intf.class

@@ -0,0 +1,10 @@
+CORE symex-driven-lazy-loading-expected-failure
+Test.class
+--lazy-methods --show-goto-functions --verbosity 10 --function Test.main
+^EXIT=0$
+^SIGNAL=0$
+^CI lazy methods: elaborate java::Test\$intf\.f:\(\)V$
+Test\$intf\.f:\(\)V\(\);$
+--
+--
+This doesn't work under symex-driven lazy loading because it is incompatible with --lazy-methods