Patch Ajax request to include headers per heroku api mandate

[quadrophobiac]

per @pezholio’s link https://api.heroku.com/apps/hello
this is intended to fix issue #10

[coveralls]

Coverage remained the same at 99.454% when pulling 6371516 on patch-for-heroku-api-changes into 76b2b26 on master.

[quadrophobiac]

So I figure a breaking issue like this warrants testing. However the existing test suite does not fail (see any one of the other PRs currently open) in light of new API changes.
Testing this locally is also fraught. Any GET to '/' results in a redirect to the live site (which is the expected behaviour, as exercised in bothan_deploy_spec and spec_helper.
The way around that is to disable some heroku .env variables, and then there is CORS to be worked around.
I tried to use Heroku review apps but then a whole can of worms opened there.
So in short - if this looks like a resolution to issue #10 can it be merged in?

[quadrophobiac]

got review apps working - this is not good to merge

[quadrophobiac]

EDIT EDIT what I said RE review apps - I'm not sure that heroku review apps can be used to test this either because they too redirect to https://deploy.bothan.io/ rather than their actual URL.
@pezholio, @Floppy I'm out of knowledge on the best practice here - what's the best way to test that this is operational in the same way it will be live.
I get the sense that the redirect behaviour is a function of heroku-bouncer, but I'm not certain. Looking for an expedient resolution to this if it exists but I don't know where to begin in terms of amending the redirect behaviour that's causing the testing issue

[coveralls]

Coverage remained the same at 99.454% when pulling d4dd150 on patch-for-heroku-api-changes into 76b2b26 on master.

[quadrophobiac]

Have tested this manually like so

• remove HEROKU_OAUTH_ID and HEROKU_OAUTH_SECRET to disable heroku bouncer middleware
• run app via RACK_ENV=test bundle exec rackup config.ru
• navigate to localhost and enter text into the Title text field. Existing apps like demo should return a 200 code, a string of characters that has no matching heroku app should return a 400

[Floppy]

Live's broken anyway so let's give it its final test there :)