Add a class to compare .dll files for *real* changes

... i.e. *not* the time stamp nor the .pdb GUID.

The problem is that recompiling *identical* code on Windows does not
result in byte-identical .dll files. The reason is that the .dll file
format *defines* time stamps to be part of the format. Even without
timestamps, there is another problem: disregarding the debug option,
Microsoft Visual C compiler still incorporates .pdb information, always,
including a Global Unified IDentifier that changes *every single time*
source code is compiled.

The DllFile class is designed to analyze .dll files and determine
whether they contain *functional* changes as opposed to circumstantial
ones, such as time stamps or GUIDs.

We need this functionality to be able to avoid uploading "different"
files every night when uploading Micro-Manager's nightly build.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Add example .dll files for the upcoming DllFile test

The empty.dll file was generated by

	: > empty.c
	gcc -s -o shared empty.dll empty.c

and adjusted.dll was generated by recompiling, followed by adjusting the
time with PE Explorer's trial version's Tools>TimeDateStamp Adjuster to
the kick-off time of one of the most exciting games in the past few years.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
WIP: Test DllFile

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
TO-UNDO (in a plane...)
DllFile: compare against a URLConnection, not a File

This makes it more convenient for the intended use case: to compare .dll files against the current version on the update site.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>