Unfortunately I didn't think ahead, and left no room in the version
numbering between 1.6.1 (for Varnish 6.1) and 1.6.2 (for 6.2). So
the package for this version will be released as 1.6.1-2. But now
we have more than one version in the history that announces itself
as 1.6.1.

The RPM spec strictly requires Varnish 6.1.

Also update set.saved(), to enable checking if an integer was saved.

re2 no longer does that since commit
848dfb7e1d7ba641d598cb66f81590f3999a555a.

compile_fail.vtc evidently takes longer than 60s when run in a
docker container.

The reason is the same as for
https://github.com/varnishcache/varnish-cache/issues/2708 :

VRT_priv_task may now return NULL for out-of-workspace errors, see
https://github.com/varnishcache/varnish-cache/commit/de2b431086a13b243dc8b3e71cd8697db1df2c7f

If RE2 reports the "DFA out-of-memory" condition for a failed set
match, the VMOD reports the error as well.

Update REQUIREMENTS to reflect compatibility with Varnish 6.0.

re2 compatibility has been tested through 2018-04-01.

No longer using the auto-generated SYNOPSIS.

Fixes parallel build failures when compilation of vmod_re2.c,
set.c or re2.c is attempted before vmodtool is finished

The terminating null byte for the C string result is written at
the index given by std::string.size() for the C++ string. It had
been written at one past that index.

WS_Release() must then ensure that the terminating null byte is
within the allocated portion of workspace.

NULL is no longer possible as an ENUM value.