Adapt code to Micro-Manager 2.0

[dscho]

As per Chris' announcement, there is an alpha version of Micro-Manager 2.0 already. The main purpose is to give users as well as developers a glimpse of things to come.

The main changes as far as the SPIMAcquisition plugin is concerned are removed APIs, but the APIs that stay should be backwards-compatible.

We need to make sure that we use only APIs compatible with Micro-Manager 2.0.

[dscho]

I believe step number 1 will be to build https://github.com/micro-manager/micro-manager from scratch... Or maybe not, maybe it is enough to extract the .jar files from http://valelab.ucsf.edu/~MM/nightlyBuilds/2.0.0-alpha/Mac/

[hkmoon]

1. @dscho & @hkmoon created mm2 branch for Micro-Manager 2.0 support. (see https://github.com/openspim/SPIMAcquisition/tree/mm2)
2. Some of 1.4 packages' classes are relocated to under org.micromanager.internal for the backward compatibility. However, we need to adapt new ways in 2.0 by removing the internal package usage.
3. @dscho made new log utility in SPIMAcquisition class instead of ReportingUtils.logError.
4. This issue will be dealt with as soon as anti-drift problem is resolved.

[dscho]

Some of 1.4 packages' classes are relocated to under org.micromanager.internal for the backward compatibility.

According to https://micro-manager.org/wiki/Version_2.0#API we must not rely on classes/interfaces from .internal packages...

new log utility in SPIMAcquisition class instead

To clarify: this uses ImageJ2's (or SciJava's) LogService via the context obtained from IJ.runPlugin(Context.class.getName(), "");.

This issue will be dealt with as soon as anti-drift problem is resolved.

We should also investigate whether there is anything behind the claims that unexplained delays happen after a couple of hours of long-term time lapse imaging.