Allow shed-tools to consume run_data_managers.yaml

[jmchilton]

Example Input File: https://github.com/galaxyproject/ephemeris/blob/master/tests/run_data_managers.yaml.sample.advanced

Update shed tools to:

• Check for a data_managers key in the source document.
• If there is, iterate over the ids therein.
• Convert IDs into dictionaries as would be expected by shed_tools to install repositories:
  • toolshed.g2.bx.psu.edu/repos/devteam/data_manager_fetch_genome_dbkeys_all_fasta/data_manager_fetch_genome_all_fasta_dbkey/0.0.2
  • {name: "data_manager_fetch_genome_dbkeys_all_fasta", owner: "devteam", tool_panel_section_label: None, toolshed_url: toolshed.g2.bx.psu.edu}
• Run through the rest of the code as if this was the input - perhaps just do pre-processing and write a temp file and literally run through the rest of the code.
• Assume everything is in the latest changeset revision initially, but maybe come back and revisit version handling to find the right chagneset in a second iteration.

Perhaps I'm missing something, but the IDC could just get away with managing two types of files (data managers execution descriptions and bootstrapping data sources (e.g. genomes)) if we could just install directly from the execution descriptions.

Follow Up:

• Do the same with .ga and .gxwf.yml files also.