Perf parse params decode text

[Uzlopak]

Based on the work of mscdex regarding the decodeText. Pretty smart how he did it.

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

[Eomm]

Based on the work of mscdex regarding the decodeText. Pretty smart how he did it.

Now sure to understand: did we charry-pick some work from the original busboy repo? - In case I would add credits

[kibertoad]

@Uzlopak Can you resolve the conflicts?

[kibertoad]

@Uzlopak what are the benchmarks agains the master?

[Uzlopak]

@kibertoad
PTAL

[kibertoad]

@Uzlopak can you run benchmark to see the perf difference?

[Uzlopak]

before:
aras@aras-Lenovo-Legion-5-17ARH05H:~/workspace/busboy$ node bench/parse-params.js
video/ogg x 2,298,591 ops/sec ±0.80% (92 runs sampled)
'text/plain; filename*=utf-8''%c2%a3%20and%20%e2%82%ac%20rates' x 257,143 ops/sec ±0.29% (96 runs sample

after:
aras@aras-Lenovo-Legion-5-17ARH05H:~/workspace/busboy$ node bench/parse-params.js
video/ogg x 2,579,688 ops/sec ±0.31% (90 runs sampled)
'text/plain; filename*=utf-8''%c2%a3%20and%20%e2%82%ac%20rates' x 330,596 ops/sec ±0.26% (97 runs sampled)

[Uzlopak]

@kibertoad
I dont know... tbh photofinish is a little bit complicated. I maybe rewrite the new benchmark in tinybench. Or can you rewrite that benchmark from benchmark to photofinish?

[kibertoad]

@Uzlopak We can rewrite to tinybench, photofinish main strength is that it allows running easily across Node versions, which is an overkill here.

[Uzlopak]

@kibertoad
can we just merge? I have no motivation to rewrite the benchmarks. Maybe create an issue to rewrite the benchmarks and slab a 'good-first-issue' label to it.