Proper handling of chunked input streams in LoggingInterceptor

[dkBrazz]

Fixes unexpected entity cutting in logs
#4034, #3306 and #3281

[jansupol]

The PR looks good. What it does, though, enables to read all the chunks from the chunked stream. That is assumingly the preferred behaviour. I can imagine a case where people do not want to log all the chunks and want to log just the first one, the way it worked now. Perhaps for performance reasons, or to keep the log small.
@senivam wdyt? Should we add a possibility to turn off logging all the chunks by the new LoggingFeature builder you created?

[dkBrazz]

a case where people do not want to log all the chunks and want to log just the first one, the way it worked now. Perhaps for performance reasons, or to keep the log small.

I think existing maxEntitySize should be enough to cover it

[senivam]

tests, provided in the PR prove that maxEntitySize works as designed, so, functionality with restricted entity size is not affected. For me it looks good.