InstData Import/GMT Picard: add downsample ratio mixin
Update MetaDB to use schema.table

Goes with UR's changes to eliminate use of the 'owner' column in the MetaDB
Configuration for GMSchema to get 'ur update classes' to work
Results from "ur update classes-from-db"

Mostly formatting/whitespace.

Some properties have updated type info, probably due to the switch from
Oracle to Postgres
re-add the trailing comma
Move 'has_optional_output' section down
change UR submodule to point to the remove-owner branch
Respect the max_records_in_ram property by passing along to picard command.  Set re_reverse default to true to match Picard default behaviour.
Fix property definition for subclass_name

The class rewriter (through 'ur update classes-from-db') got it wrong
change UR submodule to point to the remove-owner-with-recent branch

Same as the remove-owner branch, but rebase onto current master to pull
in changes necessary for SoftwareResults to calculate their lookup_hash
correctly
Merge branch 'master' into ur-update

Conflicts:
	lib/perl/Genome/Config/Tag.pm
Downsample Ratio: update the downsample ratio mixin to be like the objects with API
GMT Picard: make _downsample_ratio_is_required class method
GMT Picard/InstData Import Downsampl Ratio: made separate class for required downsample ratio; updated errors; added tests
InstData Import: rm comment from basic bam downsample test
Move the modules/tests in postprocessing to be under command
Move the modules/tests in postprocessing to be under command
Merge remote-tracking branch 'origin/master' into downsample-ratio-mixin

Conflicts:
	lib/perl/Genome/InstrumentData/Command/Import/Basic_bam_downsample.t
Merge pull request #27 from ebelter/downsample-ratio-mixin
Merge pull request #63 from dufeiyu/rm_postprocessing

Remove the VR/PostProcessing