At least "work" in the sense that varnishtest does not obviously
break, but since it doesn't test the utils at all (but does use
the varnishapi) more work & testing will be needed.

and copy them to the "real vsm" when we create it.

it via heritage.

again.  Much still outstanding.

but varnishapi and users do not work yet.

other way than -l does you no good.

of the fact that we have so many params in units of bytes which
you cannot tell "64k" so now you can.

Notice that a couple of specialist params (fetch_chunksize and
fetch_maxchunksize) have changed units from kilobytes to bytes,
but the default values are the same.

Fixes	#1060

output buffer is full.

This isn't needed since we no longer use VRE_NOTEMPTY_ATSTART

This reverts commit 43b009a8.

transferring huge amounts of data, and it should not be used that
way.

But we have commands like ban.list which potentially can return at
metric shitload of data and this is a problem.

This commit implements a cli_limit paramter which (with its upper
limit) protects from responses that cannot be moved by the CLI
protocol no matter what.

We set the default to a low 4096 bytes, in order to make people
specifically shoot their feet off if they really want to see 200k
bans.