Previously, "HTTP response status" was rendered of a subsection
of "storage", which is wrong, they should be on the same
level, or at least not in that order.

We now use the order = - ~ for section, subsection, subsubsection which
we also use in other places like vcl(7) and which is in line with
the example in https://docutils.sourceforge.io/docs/user/rst/quickstart.html#sections

This prevents unecessary docs builds.
However, we do need to touch the *if.c mtime, otherwise a
doc-only change will cause vmodtool to run on every make afterwards.

Relevant to: #3901

URLs are getting longer and longer...

ref: da455434

with uds abstract sockets, sun_path should start with a NULL character followed
by the socket's name. The name is not considered to be NULL terminated and can
contain NULL bytes which have no special meaning. socklen is used to determine
the length of name and must be set to the length of the struct sockaddr_un up to
the last character of name, otherwise the 108 characters of sun_path will be
treated as the name of the socket, including NULL bytes.

m00002.vtc has long been renamed to vmod/tests/std_b00001.vtc,
so we could also reference that test case, but I guess a debug
CLI command should be warning enough...

to anchor patches

Releasing 7.3.0

- I think the excellent ESI processing changes documentation should
  be promoted from changes.rst. I think it is more helpful to
  users planning their upgrade, because it gives better advice.

- I thought we could be a little more verbose on abstract UDSes
  and the weak Last-Modified changes.

- The director .release callback was not yet mentioned

All other changes are not worth mentioning I guess.

At least for me, this makes it easier to check if we missed anything.

- cross-reference parameter and vcl variable

- clarify that a zero value means no limit (I found 'no buffering' confusing when
  in fact the full object is buffered, potentially)

- improve wording, hopefully

The square brackets were probably the result of copy-pasta from vcl.load
where the initial state is indeed optional.

Before this patch, layered directors needed to be destroyed top to
bottom, and whenever that order was missed, we would panic, because a
to-be-destroyed director still had references to it.

One special case where this issue would always trigger are looped
directors. Those should not be used and will cause havoc, which is a
separate issue #3899. But we should still be able to unconfigure such
a configuration.

We solve the destruction order issue by making it a two step process:

When a director is destroyed through VRT_DelDirector, a new release
function is called, which has to disassociate any backends. The
director then loses a reference, and when all references are gone, the
destroy function is called.

The new callback would not be necessary for the cases in varnish-cache
today, directors could simply disassociate any backends before calling
VRT_DelDirector. But this would complicate or even make impossible
transfer of director ownership, where the code responsible for
creating a director is not the same as the one calling
VRT_DelDirector(). As a side effect, it also helps clarity.

Fixes #3895

The last reference to a director might go away with VRT_DelDirector
_or_ VRT_Asssign_Backend, which the former needs to account for.

We assert for the VDIR_FLG_NOREFCNT case that there was only one
reference such that a single deref yields no reference left.

Part one of the fix for #3895

This is in preparation of follow-up commits. Reasoning:

- in both call sites, we already use the struct vcldir *
- once call site actually used TAKE_OBJ semantics, but those
  can easily be moved

Use a local vdir variable for clarity like elsewhere in the code.
Use the lock in vdir, not the pointer to it in VCL_BACKEND for
consistency with VRT_DelDirector() a few lines above.

I noticed that users, apparently, have no way of finding out what
their distribution configured?

Now that we broke the VSL format, this is the time to act.

This prevents VUTs from attempting to read incompatible formats, while
preserving the current header size, aligning it with the SHMLOG header
at the format number 2.

It will no longer be valid for assignments, and in one case the
assignment was superfluous.