Changes in Android Launcher to support obfuscated fonts

These changes piggyback on the changes recently checked in
the feature/AndroidByteRangeStream branch for Radium-SDK.
In that set of changes, we modified the code in Readium-SDK to
support obfuscated fonts in Android. We did so by modifying the
code in the JNI layer to make use of Package::GetFilterChainByteStream().
However, this required other changes, which modified the interface for
the JNI layer and as such required modifications in the Launcher itself.
This checkin contains those changes.
Merge branch 'develop' into feature/obfuscatedFonts
Use the new WIP API for etching all resource data as a full byte array from the SDK side.
Update sub module.
Support for byte ranges in the Android Launcher

This checkin includes some changes that will allow the Android launcher
to support byte ranges. In a nutshell, the Package class from Readium SDK
will return a ByteBuffer to the EpubServer, when a range request has been made.
The EpubServer code will get that ByteBuffer and put it into a
ByteArrayInputStream, and that will be the InputStream that will be returned to
the Nano HTTP Server.
Use fetched bytes for non-html resources.
Return empty stream if resource data was not found.
Merge branch 'feature/getAllBytes' into feature/obfuscatedFonts
Use new PackageResource API in EpubServer
Merge branch 'develop' into feature/obfuscatedFonts
Update sub module
Update sub module.
submodule

Conflicts:
	readium-sdk
fixed mime type (now extracted from manifest item content type)
fixed HTTP url handling
fixed relative path resolving
changed localhost to 127.0.0.1 to avoid connectivity issues (domain name resolve when device is in plane mode)
NanoHTTPD class tabs vs. 4x-space separator consistency (the main codebase ; besides this class ; is totally inconsistent, about 50-50% ... needs harmonising)
separate HTTP range header parsing fields, to collect both start and end successfully
latest version of NanoHTTPD + moved "if" condition for empty/null URL
handling of "if-none-match" and "if-range" HTTP headers suppresses error "MediaResourceGetter Invalid url: java.lang.RuntimeException: setDataSource failed: status = 0x80000000", however the MediaServer StageFright still goes into infinite loop and the app eventually crashes (SIG).
Leaving buffer read log messages in NanoHTTPD, so we can debug the process (needs removing when we're done).
removed obsolete TODO comment
added temporary log messages, fixed HTTP ETag (now based on file path as well), moved mime-type code higher up (cleanup)