Not sure if we should backport the .get() fallback change, but if we
want to, this commit should do it.

Because we can not provide defaults for all types, .get() might trigger
VCL failure now.

Note that the interface is fully compatible with existing VCL, but while
previously a missing fallback argument would trigger a compile time
error, it will result in a VCL failure now.

The types without a default which might trigger a failure are:

* ACL: Trying to match a NULL ACL would trigger a failure in
  varnish-cache anyway

* BODY: Due to the lack of examples, it is unclear what a NULL body
  would look like

  A sensible default might be added later (maybe the empty body?)

* HEADER: A default makes no sense

- Include the Varnish default vmod_path in the varnishtest command.
- Non-generated VTCs are also distrubuted.
- Clean the .dummy file.

Ref:
https://github.com/varnishcache/varnish-cache/commit/681c11998ec56dc4460a30585210f95a7850ea3b

we use a single malloc for struct vrt_blob and the blob data it points
to

- support out-of-tree builds
- explicitly define required sources
- differentiate built sources
- avoid temporary files in srcdir

... now that the name clash is resolved

Ref: https://github.com/varnishcache/varnish-cache/commit/5450550906d0809dfc21ae9d3a5b14446c1809d4

This reverts commit 532fdef2.

Ref:	d67993451bda7eeb7c0ea3c5528a8353f283a190

ref: 0c74d1b99f1f43fc99725fe14322760afa7858ee

Ref: e8985f22711fe9a342b27a10052ae3655f64435c