Fix inconsistency in Perlbal deployment example.
Thanks to Slaven Rezić for spotting this.
Merge pull request #884 from racke/pr/perlbal_deployment_example

Fix inconsistency in Perlbal deployment example.
Added .travis.yml to MANIFEST.SKIP so t/manifest.t passes.
A new settings, global_warnings was added to replace import_warnings, as
the function globally enabled warnings the same way as -w/$^W does, this
seems more clear.  The documentation was updated to this affect.

import_warnings was deprecated in favor of the more clear global_warnings
to turn global warnings on and off through $^W.  The code still exists,
the documentation was updated.

The import_warnings/global_warnings functionality is now off by default.

Dancer's import() function now exports warnings, which is documented
behavior, however was left out of the function.  As global warnings
were previously enabled by default, I foresee no issue with this
affecting any current user applications.

Test cases for this behavior were added.
Changes for Travis CI

The CI seems to enable $^W, which goes against the "Dancer has it
off by default."  I've removed the test as a result.
Now with removing them...
Merge pull request #888 from symkat/ManifestCleanup

Added .travis.yml to MANIFEST.SKIP so t/manifest.t passes.
Merge pull request #887 from symkat/GlobalWarnings

Cleaning up the warnings settings.
Marking import_warnings deprecated

As suggested by yanick, import_warnings is marked as
deprecated and will emit a warning on its use.

I've added myself as a contributor to the author file for work on
https://github.com/PerlDancer/Dancer/commit/9aee1c73365b876b7110253e6363a5f7a5078c02
add 'private_key' to the list of potentially sensitive keys
Merge pull request #892 from tomheady/devel

add 'private_key' to the list of potentially sensitive keys
Merge pull request #890 from symkat/import_warnings_deprecate

Marking import_warnings deprecated