We were tolerating some unintentional ESI behaviour due to the
xml check hitting.

We now either avoid running into the xml check or specifically
test that we are hitting it.

In addition, add some logexpects to tighten checks

ver_p depends on the amount of data we have read ahead, so it is not
suitable to get predictable results for ESI testing

for the default symbolname prefix ("vmod_")

This should help the transition for VMOD writers that rely on the
SHA256_* functions.

Fixes #2468

Sort various lists

This reverts commit 83425a05.

This is similar to `varnishd -x optstring`.

Refs dc5fe3b

This helps write scripts like this:

    optstring=$(varnishd -x optstring)

    while getopts $optstring opt
    do
        case $opt in
        n)
            # handle $OPTARG
            ;;
        # handle other options
        *)
            # ignore unneeded options
            ;;
        esac
    done

    varnishd "$@"

Otherwise if optstring is not kept in sync, getopts will stop processing
options if it encounters one that is not specified.