increase HTTP server's default maximum POST size to 2MB

[spoonincode]

I'd say at least once a month I see a user ensnared by the HTTP server's default maximum POST size when trying to set a "large" (512KB-1MB) contract on their account. There's even a recent open issue in b1's repo with someone who fell victim to this trap (EOSIO/eos#11085)

The reason this problem creeps up is because the WASM in the request sent to the HTTP server in keosd is encoded as a hex byte array, effectively doubling its size in the POST payload.

#153 improves the error message in this situation. But I really can't see any downside to just increasing the default limit to 2MB. This allows users to set contracts up to just under 1MB in size -- the maximum size cleos can set contract code to as-is anyways. A 2MB instead of 1MB limit would even seem unlikely to impact a nodeos RPC node exposed publicly with no proxy protection in front of it.

[spoonincode]

something bad with that test on main from which this was branched. fix is over in #144's ba933de so once that PR goes in I'll merge in the fix here

[poplexity]

Does keosd also use the http plugin? Only thing worse than understanding the unclear error message is finally figuring it out and updating the setting on nodeos just to keep getting the same error message after updating nodeos because keosd is still failing.

[heifner]

Does keosd also use the http plugin? Only thing worse than understanding the unclear error message is finally figuring it out and updating the setting on nodeos just to keep getting the same error message after updating nodeos because keosd is still failing.

Yes, keosd uses the same http plugin.