Apparently, clang11 on i386 macOS uses `int` instead of `ssize_t` for
`a- b` where bot `a` and `b` is `char`. It leads to an error:
```
vtc_http.c:392:8: error: format specifies type 'ssize_t' (aka 'long') but the argument has type 'int' [-Werror,-Wformat]
                            p - hp->body, t, *p);
                            ^~~~~~~~~~~~
```

Cookie name and value are separated by equal sign, not colon.
Signed-off-by: Dridi Boukelmoune <dridi.boukelmoune@gmail.com>

I adjusted the docs to reflect the removal of spurious trailing
semi-colon from the generated cookie string.

Closes #3754

The separator between cookies in a cookie header is "; " and we should
not generate it in a way that adds a spurious ';' at the end of the
cookie list.

Refs #3754

We no longer pass coverage flags to cc_command.

This puts them closer to the 'NEXT' marker to lower the risk of
overlooking them in the release process.

This tweaks the workflows in circleci so that the same configuration can
be used both in the regular master workflows and the release branches,
removing a brittle release process step of editing there.

Releasing 7.1.0

from 7615e559 - sorry

This reverts commit 8f11c925.

And while at it, make it easier to work with distribution names with
less if statements and more case matching.

Better diff with the --ignore-all-space option.

Removed one paragraph which was really confusing and, I guess, wrong:
IIUC, backend references _always_ need to be taken with VRT_Assign_Backend,
because the referencing vmod can make _no_ assumptions about the assigned
backend.

Also I hope to have clarified use of VRT_StaticDirector().

I found the previous wording confusing and hope this is considered an improvement.

We should make clear that lack of onerror="continue" implies abort only if
the feature flag is set.

Refs varnishcache/pkg-varnish-cache#154

Thank you do Dridi for his work on the release documentation.

I have gone through all commits and reused some wording of his
where appropriate.

As before, the changelog should roughly match the commit order (from new
to old).

It was increased in 635f9f20 to avoid
sanitizer suppressions to scroll out of screen the lines we expect to
find, but on some 32bit ARM system it makes the test even less stable.

Refs #3788

Working on the release notes I realized that there was nothing
actionable to prepare for deprecated aliases in future releases.