DA: Decide on input format & process inputs

## Summary

The inputs to the DA on launch contain all the information necessary for a debug session. Deciding on the exact format of these inputs and how they passed to the DA is the basis of this issue.

## Completion Criteria
* Command-line inputs to the DA server process are defined. We know this must include:
* Simulate trace file
* Source maps for programs that were run
* A way of pairing programs bytecode (i.e. logicsigs, approval programs, and clear state programs) to the provided source maps. **NOTE:** likely we will enforce a constraint that every program ran must have a source map at this time for simplicity.
* The DA can read, process, and store information related to the inputs.
* Based on the provided trace file, the capabilities of the DA may change. For example, if the trace file does not include stack values, the DA has no way of reporting this information. This is only relevant during development as we add information to the trace. Ultimately the DA will expect a full-featured trace.

## Questions
How to pair program bytecode to source maps? Options we can think of include:
* App ID?
* Hashing something w.r.t. TEAL byte code?