much remains to be done

ved_ is used in varnish-cache

there also was a stupid precedence error in PF_CFG_DEFAULT :(

docs are still WIP

Remove the increased thread_pool_min setting where it's not needed,
and fix indentation.

we now get the flags from vcl once when we init the pesi vdp

this should preserve existing functionality, but is not complete with
regards to the configuration from vcl.

we want to delay destruction until we have delivered all of the
worklist, but we need to fini the vdps in the same order as
varnish-cache serial esi.

the error case is gzgz which needs to update the parent at the right
point in time

using the paren't was wong

in this context, req is the unpender, but we need to push to the crc
node's parent

See comments in the test about unfortunate limits using vtc to
test gzipped H2 responses.

Repeating the test in e00019.vtc with HTTP/2 fails both here and
for standard Varnish. My understanding of HTTP/2 is too poor for
me to know whether there is a bug in a Varnish, or if I am not
applying HTTP/2 correctly. More details in the comments of the vtc.

Setting this aside for now, but we should come back, but we should
come back to it (and if necessary file a Varnish bug report).