wire these integration tests to the tests/python/pants_test:integration target

"All integration tests should be wired up to the tests/python/pants_test:integration target, I think."

oh yeah, good idea; that's probably what it's there for, d'oh

Testing Done:
./pants tests/python/pants_test/BUILD:integration

Now runs fou^W FIVE tests.

Reviewed at https://rbcommons.com/s/twitter/r/543/
travis CI mail += lhosken

reviewed at https://rbcommons.com/s/twitter/r/552/

but patched in by hand like an animal
Fix resources path in src/python/pants/BUILD:pants_transitional_publishable_library target consumed at twitter

Bugs closed: 245

Reviewed at https://rbcommons.com/s/twitter/r/544/
Add benjyw@gmail.com to travis ci emails.
Convenient scripts for working with rbt.

Prevents having to memorize flags, and saves some editing in the web form.
encourage folks to add themselves to .travis.yml

Testing Done:
./build-support/bin/publish_docs.sh -o # oh pretty

Reviewed at https://rbcommons.com/s/twitter/r/557/
Break out stty settings handling into a utility.

So we can reuse it for python REPL running, eventually.
Fixes the bug where pants doesn't recognize build targets on top-level directories.

The previous argument parser naively simply checked whether a command-line argument contained a slash (/) or a colon (:). This is a reasonable assumption most of the time, but in the case where a BUILD file is located only one directory deep, (eg, buildroot/folder/BUILD), this makes it impossible to run pants on the target simply by calling (eg) ./pants goal bundle folder.

See github issue for example: https://github.com/pantsbuild/pants/pull/159

This fixes it by actually checking to see if a phase with goals is defined by the command-line argument. It still checks before that whether the argument contains a slash or a colon, because that if an argument has those characters it can't mean a goal. But an argument not having those characters doesn't mean it is a goal.

In a completely ambiguous situation (eg, given a command argument 'bundle', and there is a valid BUILD file at bundle/BUILD), we err on the side of the goal, and print out a warning. This makes sense, because it allows the user to disambiguate the situation using the '--' syntax.