[EASY] Bump response size limit

[MartinquaXD]

Description

Since October 6th we see alerts like Failed to buffer the request body: length limit exceeded indicating that the response returned by multiple solvers (oneinch, zeroex, paraswap, balancer) is too big for the driver.
It's unclear why this suddenly started happening on a Sunday where nothing gets released or why it only seems to affect dex solvers but making the max response size configurable seems like a reasonable thing to do regardless.

Changes

• Made drivers response size limit configurable and increased the default value by 3x.
• Added trace log to print responses that exceed the limit to easily debug this the next time this happens (disabled by default but be temporarily enabled without restarting the pod)

How to test

e2e test covers parsing of the new config parameter

[m-lord-renkse]

Do we have in the logs the size of the responses? did they suddenly jump or the increase was progressive? The previous default value of 10 MB seems relatively big 🤔

[MartinquaXD]

No, we don't have the size of the response as metrics or logs. We stream the content in chunks and abort when we exceed the limit so we don't know what the total size would be.