fix(core, middleware-body): incorrectly parsed querystrings

[JozefFlakus]

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

• @marblejs/core - the query parser cannot parse complex URL encoded strings, like:

foo[bar1][baz]=test1'
foo[bar2][baz]=test2'

• @marblejs/middlware-body - URL parser incorectly decodes complex application/x-www-form-urlencoded strings like:

foo[bar1][baz]=test1'
foo[bar2][baz]=test2'

or

foo=some=value&which&is=complex

What is the new behavior?

• @marblejs/core - integration with qs library (a querystring parser with nesting support)
• @marblejs/middlware-body - ☝️

Does this PR introduce a breaking change?

[ ] Yes
[x] No

[codecov]

Codecov Report

Merging #104 into next will not change coverage.
The diff coverage is 100%.

@@         Coverage Diff         @@
##           next   #104   +/-   ##
===================================
  Coverage   100%   100%           
===================================
  Files        87     87           
  Lines      1027   1008   -19     
  Branches     81     80    -1     
===================================
- Hits       1027   1008   -19

Impacted Files	Coverage Δ
...ges/middleware-body/src/parsers/url.body.parser.ts	100% <100%> (ø)	⬆️
packages/core/src/router/router.query.factory.ts	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c9dafb...f087008. Read the comment docs.