Fix jsonp content-type response header

Incorrectly sends application/json rather than application/javascript on a jsonp request which breaks strict mime handling. In response to error: Refused to execute script from '...url...' because its MIME type ('application/json') is not executable, and strict MIME type checking is enabled.
Offload WordPress installation to bash script so it can be reused
Run tests against single site and multisite
Support for running tests in a few ways
Change our plugin activation test
Improve tests for multisite
Check that the JSONP callback is a string first

If you pass in an array, this would cause a warning.

Props @ircrash
Resolves #409. Now matches dashes in addition to alphanumeric and _ characters
Refactored regex to use \w again and simply add - to the group
Updated Tests to check for the updated keys, moved old keys to deprecated list
Or maybe they shouldn't be listed in deprecated and checked
Fixed deprecated keys... to use the newer route
Travis pointed out my typo in the deprecated field
Merge pull request #405 from WP-API/double-check-jsonp-format

Check that the JSONP callback is a string first
Add newline
Different type, per Ryan's request
Add steps to readme for executing tests with vagrant ssh -c
Merge pull request #380 from simonlampen/master

Fix jsonp content-type response header
Merge pull request #410 from EdHurtig/master

Match dashes in addition to alphanumeric and underscore
Merge pull request #416 from kadamwhite/testing-from-outside-vagrant

Add steps to readme for executing tests with vagrant ssh -c