Fixed synchronization mechanism to use streaming capabilities to
avoid caching response on file.
Test was mangling date. This is now being handled correctly by
the VictimsRecord format string and no longer required.
Make v2 URLs work
Update default to v2 URL, remove debug code
Addresses the following issues:

- The query for matching classes against a known vulnerable artifiact
  was not working correctly.

- Metadata was not being correctly extracted from the MANIFEST.MF file.

- Comparing by a crude entire file hash was restored, allows for quick checks.

- Removed tolerance as no longer required

- Switched to using H2 instead of Apache Derby.
The file hash was not getting correctly marshaled from the victims-web
response and inserted into the database.
- Fixes for filehash mechanism.
- Renamed IOUtils as is Apache project name clash
- Temporarily disabled test
- Additional query for metadata against the victims.name and
  victims.version entries (mimic v1).
Re-enabled test case with working test data.
Updated sample app POM to reference enforce-victims-rule 1.1 and the v2 database
Update README.md to reflect new options for v2 backend
Fixed formatting
[maven-release-plugin] prepare release enforce-victims-rule-1.1
Fixed up SCM, artifact name and details prior to performing a maven
release
More release fixes
Release as victims-enforcer
Fixed SCM URL?
Release tweaks
Fixed issue with SCM URL
Grr...
[maven-release-plugin] prepare release enforce-victims-rule-1.1