fix(readBody): handle top-level arrays in url-encoded data

[danielroe]

🔗 Linked issue

resolves #275

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Previously a valid url-encoded string with multiple entries for the same value was not properly parsed. This creates arrays in such cases; it still doesn't support advanced nested arrays like qs but handles this specification as expected.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codecov]

Codecov Report

Merging #278 (e09702a) into main (c747f5c) will increase coverage by 0.23%.
The diff coverage is 100.00%.

❗ Current head e09702a differs from pull request most recent head 74caf25. Consider uploading reports for the commit 74caf25 to get more accurate results

@@            Coverage Diff             @@
##             main     #278      +/-   ##
==========================================
+ Coverage   75.94%   76.17%   +0.23%     
==========================================
  Files          20       20              
  Lines        1218     1230      +12     
  Branches      224      228       +4     
==========================================
+ Hits          925      937      +12     
  Misses        293      293              

Impacted Files	Coverage Δ
src/utils/body.ts	86.04% <100.00%> (+2.26%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[alphaelf]

on this line and this line can we use destr to store typed value instedof string value?, for now the undefined, true, false, null, ... values will returned as string