Can leave orphaned temp files

The BridJ library used by OpenImaj extracts the native libraries from included jar files to a system and user dependent temporary location. Because of our odd extension setup (which it isn't expecting) it is sometimes unable to remove the temporary files once its run is complete. The files can be removed by normal processes that remove temp files (system cleanup, etc) but we should avoid leaving a mess if we can.

The core issue as I found it was that BridJ hooks into the Java system shutdown event where it runs the cleanup. The problem is it runs without the jar class loader that NetLogo used to instantiate the extension, so it fails. Our options are pretty limited; either updating BridJ to allow us to provide the class loader to use at shutdown, or we can remove the files ourselves by trying to mimic where BridJ places them.

Or, we can drop BridJ/OpenImaj entirely and forget about this issue.

No source file or test is named. Start by tracing the BridJ/OpenImaj native-library extraction and shutdown cleanup, then compare that behavior with the extension's class loader. Check issue 32 before choosing an approach; done means avoiding orphaned temporary files or removing the dependency entirely.