This is in anticipation of removing the rule that a viking service
implements an Ingress if it's the only one in the entire cluster.
This can cause unexpected changes if something unrelated in the
cluster is changed, for example by independent teams working in
different namespaces.

This makes it unnecessary to undeploy the viking service that always
runs in namespace default during e2e tests (which was just such a
dependency).

The docs are not currently up to date on this point.

These are internal values of the Varnish/klarlack container, which
can be set differently with environment variables. Probably in nearly
all deployments, they will be left with the defaults.

- http target port (Varnish listener address)
- varnishadm port
- config check port
- readiness check port
- admin secret directory and file name

Make them independent on the order of execution, and do not depend
on deleting and finally re-installing the viking Pods in namespace
default that otherwise run throughout the e2e tests.