feat: adding parsebody base on header capability

[flozero]

First draft pr for #40 and #43 (I think we can make it modular enough to handle multiple header type)

I have created the parseBody function that parse base on the opts send to useBody that check also the opts correspond to the content type header also

Still new to TS and jsdocs so needs to be improve if the solution looks ok

TODO:

• improve the doc
• improve typing

[pi0]

Hi @f3ltron thanks for PR. I think we can keep using single useBody (inlining logic) (that is also parsing body) to avoid confusing between two utils

[flozero]

I was thinking about extracting it to accept more header type not supported from the default json one. It's a bit a mess my code still. Will work on it step by step

[pi0]

@f3ltron Are you still working on this branch? If not can do refactors and merge :)

[flozero]

I am not you can do the refactor for sure @pi0