Adds PHPUnit Configs to Report Code Coverage

Making sure that every NoCrupht is thoroughly tested is very important.
Code coverage reporting will help keep up with this idea.

Configurations are added to phpunit.xml.dist to collect code coverage
information on the src/classes directory and display coverage summary to
standard output, as well as to an xml file, which will be used to
programmatically check if code coverage is satisfatory, and also html
coverage reports will be generated too.
Adds Script to Check Testing Coverage

Added coverage-check.php script that can programmatically determine if
coverage is satisfactory.
Ignores Build Artifacts

We don't want to track build artifacts.
Moves Some Files Around

Now there are three main directories:

+ src: holds the actual valuables that we are developing.
+ tests: tests the valuables we are developing.
+ build: holds junk used or produced by build process (which only includes
testing for now).

You might ask, "Why not put tests in build too?", since they are part of
the build process, and in fact, the only thing involved in the build
process at this point. The reason I didn't put them in build is for
visibility. I want the tests to be seen. I want developers to immediately
know that testing is a part of this project -- important enough to place a
directory in the top level.
Adds Coverage Check to Travis

Adds configuration to run coverage-check.php as a build script. The script
will trigger build failure if coverage is not sufficient.
Adds Travis Config for Artifact Upload

Configured travis, after failure, to upload build artifacts to AWS S3, so
that they may be reviewed.
Updated Travis Artifact Upload Configs

The artifact upload was erroring out.
Maybe This Will Work?

I'm having trouble getting env encryption to work ...
Merge pull request #12 from NoCrupht/TestCoverageCheck

Test coverage check