Use query-string instead of qs

[mjackson]

Fixes #121

[taion]

How do you want to handle arrays and null here? query-string handles them just fine (though stringified differently from qs in both cases).

[timdorr]

It looks like it handles those sanely. This is just a developer convenience warning, so they're aware we're not looking to handle nested queries. I wouldn't try to go overboard on supporting a bunch of edge cases here. I think they'll figure it out when they see %5Bobject+Object%5D in their URLs 😄

[timdorr]

@mjackson Feel free to smash that commit. I don't know how you like your commit history. I'm more of a multiple-commit kind of dude, but you may want it clean.

[taion]

@timdorr Regarding your line comment that got eaten, what I meant was we should probably not warn in those cases, because query-string is sane about handling them.

[timdorr]

Duh, because arrays are typeof object. I always forget that. Let me amend that commit then.

[taion]

Arrays and null. I usually just do p instanceof Object.

[timdorr]

But [] instanceof Object === true

[taion]

D'oh. Let's squash and merge this then.