Fixes for bio-formats build/eclipse
Refactor TestPythonImporter for re-use
Add Memoizer usage to OMEROWrapper
FielSerializer in OMEXmlModelComparator. Possibly unneeded
No longer close reader in ImportRequest
Activate DEBUG logging for Memoizer
Add Memoizer to BfPixelsWrapper and PixelsService
New-style (temp) Kryo configuration
Trace logging in cli
Add missing OMEROWrapperTest
General OMEROWrapper refactorization for passing directory

Reduce the number of locations that OMEROWrapper is created,
passing directory when it is clearly server-side.

Note: this currently does not compile because the OMEROWrapper
lives in blitz while everything else lives in romio.
Split OMEROWrapper to CachingWrapper for directory use

To simplify cleanup, having all caches written into a single
directory was added to the `loci.formats.Memoizer` class. Here,
hard-coded as `/tmp/memo`.

The various import related classes, howerver, are a tangle of
dependencies making it very difficult to not copy the same block of
code, e.g. the ReaderWrapper sequence and setting the proper
directory, throughout the code base.

By splitting OMEROWrapper into a CachingWrapper part in romio with
no dependencies on blitz we can mostly do this.

A few issues:
 * now, client-side caching is disabled
 * requires an insight dependency on romio
 * enforces use of a wrapper through ome.io.bioformats
 * allowed for preliminary, needed import class cleanup:
    - use of `wrap()` is encouraged
    - overriding `ReaderWrapper` method is discouraged
    - discourage holding on to wrapper instances
Fix slf4j rebase issues
Fix ClassCastException in OMSC
Merge remote-tracking branch 'origin/develop' into fs-file-caching

Two branches both tried to refactor the copy-n-paste
issues with reader creation. The combined solution means
it's possible to override createBfReader, but by default
a simple CachingWrapper will be returned.

A rebase would have been unduly arduous since in the early
commits of the fs-file-caching branch the CachingWrapper
which would be needed wasn't present, making bissecting
later impossible.

Conflicts:
	components/romio/src/ome/io/nio/PixelsService.java
Revert "Split OMEROWrapper to CachingWrapper for directory use"

This reverts commit 6f69e3843e790b0481cae71e032d789984cf8cbe.

Conflicts:

	components/romio/src/ome/io/bioformats/CachingWrapper.java
	components/romio/src/ome/io/nio/PixelsService.java
Revert "General OMEROWrapper refactorization for passing directory"

This reverts commit d37c4c7806ccd81013eeaaf7940e05c4db2328f3.
Minimal refactoring; limits where Memoizers are created

There is almost certainly more cleanup that can be done in terms of
where the reader stack is constructed and how it is stored.  This is at
least a start, and is hopefully safe and minimally invasive.

See #10750.
Merge pull request #19 from melissalinkert/memoizer-refactoring

Memoizer refactoring
Production-location for Memoizer cache files

This removes the last location with /tmp/memo hard-coded.
Along with a change to Bio-Formats, caching will only
occur when a directory is explicitly set. With the current
setup, this means that caching does *not* occur during:

 * client-side import
 * server-side import
 * any where in Bio-Formats natively

The only time memoization should occur is in the ome.io
(i.e. romio) package during rendering and pixel reading.