VariantReporting subsystem works on files not just builds

The ResourceProvider replaces the build, at least conceptually.  Running
on a build will consist of generating a ResourceProvider first, and then
running the subsystem.  This commit is a regression in that sense,
because running on a build has been disabled for now.

The ReportGeneratorWrapper goes away entirely, since translations can be
provided by the ResourceProvider.

Expert commands accept files instead of objects for the most part, and
when they need objects from the ResourceProvider, they are given ids
only.
remove wait statement from test
VariantReporting Expert Commands shortcut properly

Properties that are considered 'paths' are hashed with the md5 algorithm
and that value is used to shortcut/produce software-results.
MasterPlan can now determine resources_required

The Expert's Adaptor Class specifies outputs as 'is_provided'.  All
Experts in the plan are then queried and the names of all such outputs
are collected.
Add test for Expert Command's lookup_hash function
Allow ResourceProviders to be read from and written to files (yaml)
MasterPlan can now validate a ResourceProvider
Dbsnp expert takes annotation_vcf instead of ImportedVariation build
Rename test from Plan.t to MasterPlan.t
Attempt to lookup allocation before md5sum'ing files
rename annotation_vcf to dbsnp_vcf
Add test_expert_is_registered to test_helpers
Add Framework/Test

These packages will allow us to test without referencing our production
experts/interpreters/filters/reporters.
add missing import
Add new command 'CreateReport'
bump version of test data for vep expert

We're not ready to allow custom_annotation_tags just yet
Move base reporter into Framework directory
Experts now 'provides_annotations'

Filters and Interpreters can now 'requires_annotations'.  This allows
for combination Experts that provide multiple kinds of annotations.  It
also allows filters and interpreters to be satisfied by any of a number
of potentially compatible experts.