Add includes of referenced SAIO bin scripts

Change-Id: I6810e69a757336a3aed0a38146c27f270fe2dde1
Merge "Add includes of referenced SAIO bin scripts"
Load constraints from cluster info dictionary

If the target swift cluster under test offers the /info API, use the
constraints derived from there. If it does not, then pull constraints
from /etc/swift/test.conf, defaulting to an existing
/etc/swift/swift.conf, as we used to.

Change-Id: Iea01c9c4b5148faa10004a240df411cbe7336a6a
In-process swift server for functional tests

Provide a way to run the functional tests using a p/a/c/o server setup
in the same process running the nosetests infrastructure.

By setting the environment variable, SWIFT_TEST_IN_PROCESS, to a true
value, the functional test set up will construct a proxy, account,
container and object server running in the same process that is running
the functional tests, ignoring any external swift service. This
in-process swift environment is akin to the one used in
test/unit/proxy/test_server.py.

Setting that same environment variable to a false value will ensure the
in-process servers are not used.

When the above environment variable is not present, and the
/etc/swift/test.conf is _not_ present (or present but empty) on the
system where the functional tests are executing, the in-process
environment will be used. Previously, if no /etc/swift/test.conf file
was found, the tests would just be marked as skipped.

Using this in-process method allows one to gather code coverage using
the functional tests to exercise code paths, in addition to the unit
tests, or more easily debug existing functional tests, or write new
ones.

The are two constraints that are changed for use with the in-process
functional tests: max_file_size is lower to roughly 8 MB and
client_timeout is set to 4s.

Change-Id: I5acd65e3068868d6509feae1d1954237d37fad45