2.0 - Base test steps

[pflarr]

Move the base steps of running a test into pavilion proper. While the command to run a test series should still be a plugin, it should just kickoff the steps implemented in core pavilion.

Each of these steps has a corresponding ticket describing implementation.

1. Get the test run configs (See 2.0 - Test Configs #49).
2. Get the series and run numbers, setup directories. (See 2.0 - Test series setup #45)
3. Write a test series kickoff scripts (See 2.0 - Scheduler Refactor as Plugins #42, write_series_script, and ).
4. Kickoff the test series (Also 2.0 - Scheduler Refactor as Plugins #42, run_series_script).
5. Exit.

Pav continues via the series scripts, which will reenter pav using pav run_series.

6. Build the test code (See 2.0 - Build Process #48).
7. Copy the test build into working space. (See 2.0 - Copy test build into working space #46)
8. Write a test script for each test (See 2.0 - Scheduler Refactor as Plugins #42, write_test_script and ).
9. Kickoff each test (Also 2.0 - Scheduler Refactor as Plugins #42, run_test_script)
10. After each test completes, parse the results. (See 2.0 - Pluggable Result Parsing #47)
11. Copy results from working space, finalize results, and delete the working space.

Depends on #40.