Adjust operational limits

[aradz44]

Creates reasonable limits:

1. Max M reduce from 2M to 256.
2. Query string depth default from 1000 to 16, Max is the same.
3. Query string bytes max value from MAX_UINT to 10240.

[allenss-amazon]

As discussed, I believe the maximum values for these limits aren't properly set in this PR.

[zvi-code]

I mainly wanted to fix the M value, is that agreed? What would be the recommended limits in your opinion?

[allenss-amazon]

For M, we know that M=1 causes a crash, so a minimum value for M of 2 avoids fixing the crash :)

As for maximum, I'm skeptical that there's any real usefulness above M=64 or 128, so any number that's close to that value is fine with me (512 or 1024 would be fine, but not like 2^20). But let's be clear, here I mean the maximum as the "default" value of configurable. The maximum value of configurable should be much higher, in case there's some odd-ball customer than needs M= to say 256 or 512.

[allenss-amazon]

Can we update or close this PR?

[aradz44]

Closing it..