Moves compileQueryParser to separate module

[wesleytodd]

Moved this functionality to a separate module so I could use it in my other package. It appears no tests were originally written, so I added some in the module. If you would like we can move this repo under pillar, or here, just let me know.

https://github.com/wesleytodd/compile-query-parser

[dougwilson]

Probably should hard-pin the qs version within that module to meet the typical version range policy (pin exact versions, but if the module is part of Express, it may float patches with ~).

[wesleytodd]

I updated that in the module, and assuming it will move into the express family somewhere I used the tilde in here.

[wesleytodd]

Anything blocking us from moving forward? Do we need to move the repo or can it live where it is?

[wesleytodd]

This change is neither breaking nor required to ship v5. This was done so that it could be used individually in another project I was working on at the time, but is otherwise not necessary. I am going to remove the v5 label and we can decide if it is worth doing later as a minor.

[UlisesGascon]

Aside of the conflict... this require a change in the HISTORY.md, but I am +1 for this idea.

[bjohansebas]

Sure, is that package going to be moved to this organization? by organization, I mean one of the three that exist.

[wesleytodd]

The original goal of this PR was primarily to allow alternate frameworks and libraries who may need it to use the official express style query parsing. I did this because we were using it in the browser at the time. Since then we as a project have decided that browser support is not currently on our priority list for express and many of the project's other libraries. With that in mind, I am going to close this. We can always re-open it latter or replace it with a new one if we change our minds.