Don't interactively bootstrap when deploying with fabric

Stop deployment waiting forever for user to anwser question.
We do actually need virtualenv installed in our virtualenv.

We're going to use it to create another virtualenv later, for the app itself.
And if our bootstrap virtualenv is created without site packages, it won't
be available from the host environment.
Fix the arguments sent to virtualenv command.

Report the virtualenv or pip command that failed.
pep8 style fixs in bootstrap.py
Allow bootstrap.py to use a pip bundle
More getting rid of references to project_dir

Replacing them with deploy_dir or vcs_root_dir as appropriate.  New
names aren't ambiguous (I hope)
Finish purging project_dir and project_root

Ambiguous terms, replaced with various others that are hopefully less
confusing ...
PEP8 fixes in fablib.py
More pep8 fixes

And using some more appropriate functions, such as the dict method
setdefault() when setting up default env dicts - this means we don't
overwrite pre-existing values
use path to south patch included in dye
You can't both write a message to sys.stderr AND specify exit code when using sys.exit().

Conflicts:

	dye/tasklib.py
Fix find | rm when filenames containing spaces are present.

Conflicts:

	dye/tasklib.py
Remove redundant spec of python path for tasks_bin

and local_tasks_bin, in fablib.  They both just launch the virtualenv,
so can be trusted to find the right python.  But need to do a little
more wiring up around the local one ...
Report the fab command that failed.
tasks.py is now installed in virtualenv bin dir, so we can find it there.

Saves working out which subdirectory of lib contains the dye files.

Also run it with its own choice of python (patched by virtualenv installer)
rather than choosing one that might not match.

Conflicts:

	examples/deploy/tasks.py
In dye/tasks.py use the environment version of python

not a hardwired one
Merge commit 'd6202f2833c6f96f1efcbaf2891133c13f8feda6'

* commit 'd6202f2833c6f96f1efcbaf2891133c13f8feda6':
  Don't interactively bootstrap when deploying with fabric

Conflicts:
	dye/fablib.py
Put recent distribute into default bootstrap package list

Required to be able to install the mysql package
Set deploy_dir in project_settings
use project_settings server_home in staging_test in fabfile