Prevent test running on symex-driven lazy loading

Currently symex-driven lazy loading doesn't emit the required warning but it should.

Author: NathanJPhillips

regression/cbmc-java/invalid_classpath/test-jar.desc

@@ -1,7 +1,10 @@
-CORE
+CORE symex-driven-lazy-loading-expected-failure
 Test.class
 --classpath ./NotHere.jar
 ^EXIT=6$
 ^SIGNAL=0$
 ^the program has no entry point$
 ^failed to load class `Test'$
+--
+--
+symex-driven lazy loading should emit "the program has no entry point" but currently doesn't

regression/cbmc-java/invalid_classpath/test-path.desc

@@ -1,7 +1,10 @@
-CORE
+CORE symex-driven-lazy-loading-expected-failure
 Test.class
 --classpath ./NotHere
 ^EXIT=6$
 ^SIGNAL=0$
 ^the program has no entry point$
 ^failed to load class `Test'$
+--
+--
+symex-driven lazy loading should emit "the program has no entry point" but currently doesn't

regression/cbmc-java/provide_object_implementation/test.desc

@@ -1,8 +1,10 @@
-CORE
+CORE symex-driven-lazy-loading-expected-failure
 java/lang/Object.class
 
 ^EXIT=6$
 ^SIGNAL=0$
 ^the program has no entry point$
 --
 ^failed to add class symbol java::java\.lang\.Object$
+--
+symex-driven lazy loading should emit "the program has no entry point" but currently doesn't