perf: replace querystring with fast-querystring

[anonrig]

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[mcollina]

lgtm

[Fdawgs]

I think we should wait until this is at a stable version (v1.x) before doing this. From the rapid progress @anonrig is making I don't think that's far off!

[mcollina]

Could you please add an option to configure the querystring module to use? Like in Fastify.

[anonrig]

Fastify was using querystringParser and this package is using stringifier. I thought of querystringStringifier but I'm open to suggestions @Fdawgs & @mcollina

[mcollina]

Thanks for opening a PR! Can you please add a unit test?

[anonrig]

I removed the last commit, this is actually implemented already @mcollina https://github.com/fastify/fastify-reply-from#querystring-or-querystringsearch-requrl

[mcollina]

lgtm did you check how much this improved perf (if at all)?

[anonrig]

@mcollina I didn't do a benchmark, but fast-querystring.stringify is 20% faster than querystring

[Uzlopak]

Can we decorate fastify with querystring and the plugins consume that instead of clustering the option everywhere?

[anonrig]

@Fdawgs I released 1.0. I think it is stable enough.

[Eomm]

Do we agree to release it as a minor version?

[anonrig]

It is a non-breaking change, if we are following sem-ver.