Add ability for transgression to pull a configuration from a specific storage path

Storage paths can be assumed to be organized like the following:
- Date
- Time
- Commit Number
- Binary

Transgression should be able to pull a binary from a specific location and have a metadata object associated with this object while running (the configuration information).

The issue names no files, tests, or entry points. Start by locating how transgression currently retrieves binaries and represents configuration metadata, then determine how a date/time/commit/binary path should be selected. Done means a binary can be pulled from a specific storage location with its configuration available while it runs.

Written by the indexing model from the issue text.