Switch p4python build to use the 2014.1 release.

We've been using code from a couple years ago. This is a simple update to the
latest release of P4API/P4Python.

Testing done: Installed this and ran the review board unit tests.

Reviewed at https://reviews.reviewboard.org/r/5819/
Make sure all sys.stderr.write calls end in a newline.

Some of the stderr writes didn't include newlines, which is required for nice
formatting.

Reviewed at https://reviews.reviewboard.org/r/5820/
Make P4PythonInstaller work on OS X Mavericks.

OS X Mavericks introduced a warning in Clang that causes builds to fail because
of incorrect arguments to `cc`. The common workaround for this is to use the
ARCHFLAGS environment variable to specify an additional -Wno-error in order to
turn this back into something that doesn't fail, but the P4Python installer
overrides ARCHFLAGS, so instead we override CFLAGS.

Testing done:
Installed from setup.py successfully for the first time since upgrading to
Mavericks.

Reviewed at https://reviews.reviewboard.org/r/5822/
Add a separate 'python setup.py build' step that uses '--ssl'

We originally didn't add SSL support to P4PythonInstaller because the first
iteration of the SSL implementation in it required passing in the library path
for openssl. They've since changed that to make the library path optional, in
which case it will search the system paths.

This change does cause P4PythonInstaller to require openssl libs, but that's a
pretty trivial change in dependencies.

Testing done:
Built and checked that the resulting .so file links against libssl. The libssl
in OS X's default path is 0.9.8, which isn't the right version, so I still get
errors when trying to use ssl: P4PORTs on my devserver, but it's actually
trying to use SSL instead of the stubs.

Also installed this on RBCommons and was able to get further along in the
verification stages with an SSL perforce server.

Reviewed at https://reviews.reviewboard.org/r/5823/