Update the test suite to work with the new CRF based extractor.

* Regenerate the expected crawler results using the CRF based extractor

* Added a config option to determine whether the extractor uses a separate Java process instead of the Java Native Interface( JNI ). The
default is NOT to use the JNI. The JNI is faster and seemed to work when I was testing the extractor. However, using the JNI is causing
the test suite to hang.
Temporarily disable test until we regenerate the expected results to work with the new CRF extractor.

See issue 6381 for details.