Make the test-suite execute run when calling `testrun` state not `git.salt`.
Don't fail if `git_commit` is not in pillar, just pull latest develop.

This allows for "by hand" states debugging.
Defining python needs to be done in testrun.sls
`source` is to check out `editable` packages into `source` dir. Install from git checkout.
The proper pip.installed setting is `editable`
Revert "The proper pip.installed setting is `editable`"

This reverts commit bcb419241ffdcb3075dab7378e1704d13bfbdcd5.

The URL should be "fed" to the name after all.
Provide `pip` mirrors in case one fails, this way the build won't.
Redirect `stderr` to `stdout`.

Since we're not doing anything special with `stderr`, lets just redirect it to `stdout` so we get test-suite output in the proper order.
Install SaltTesting 0.5.0
Pip mirrors as a list is only supported in current develop and the upcoming 0.17.0
`unittest2` is only needed for python < 2.7
Jinja2 does not know what a tuple is in a template context.
Point to `python.pip` not `pip`.
Version comparison needs to be done differently in a Jinja template context.
Under CentOS/RHEL 5 the python binary to use is `python26`.
Add `curl` to the packages to install
The python binary name resolution code is now importable and reusable.
We're not specifying the name.
Install setuptools and pip using it.

CentOS/RHEL 5 does not have a proper pip package for python 2.6
We need to test against string not int.