Read the configuration once for all func tests

Merge the swift_testing module into the functional test module itself,
so that we can read the configuration once for all unit tests, sharing
the same constraints.

Change-Id: I9fbbfdade9adca329cd79f7d4291ba009327c842
Move module level setup under setup_package method

Perform all the package level test setup under the setup_package
method so that we only read the configuration file on disk when
functional tests are run. This let's us "play nice" with other tests.

Change-Id: I699d664bcef6754aac4ec6877830e745b764342f
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.

By setting the environment variable, SWIFT_TEST_IN_PROCESS, the
functional test set up will construct a proxy, account, container and
object server running in the same process as is running the functional
tests, ignoring any external swift service.

This patch also changes the behavior of the functional tests such that
when both /etc/swift/swift.conf and /etc/swift/test.conf are _not_
present on the system where the functional tests are executing, an
in-process functioning swift environement will be established, akin to
the one used in test/unit/proxy/test_server.py, and all the functional
tests will be executed against it.

Previously, if no /etc/swift/swift.conf and /etc/swift/test.conf files
were 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.

Change-Id: I5acd65e3068868d6509feae1d1954237d37fad45