Characterization fixtures for the name tree (owner order and parent chains).

These tests pin what validns prints for zone shapes that any change to how
owners are looked up or created must leave untouched.  Expected values in
src/t/test.pl are characterization values: what validns prints for these
shapes.

shapes.zone (apex shapes.example., unsigned; run with
-s -p occluded-records -p cname-other-data):

  x       A, other owner, then CNAME: non-adjacent CNAME conflict
  y       A, an out-of-zone record (rejected), then CNAME: the conflict is
          still reported across the rejected record
  c, a.b.c, m.b.c, n.b.c, b.c
          implicit non-terminal b.c created by a.b.c, given a TXT later
  www/WWW the same owner in two letter cases
  a\.b.esc  escaped dot in a label: rejected by the parser
  cont2   blank-owner continuation after a different owner
  del, deep.sub.del
          record occluded by a delegation, with an implicit parent sub.del
  $INCLUDE shapes-include.zone, then r.inc
          implicit parent r.inc created inside the include, given a TXT
          after it in the including file
  aa, x.bb
          a new name whose parent (bb) has the same length as an earlier
          owner (aa) but different text: the parent must come from the
          name, not from a length match
  d1.sib (NS), d2.sib (A)
          sibling names under the implicit parent sib: a delegation at one
          sibling must not make the other occluded, so the parent of d2.sib
          is sib and not d1.sib
  p.cc, q.dd
          a new name whose parent (dd) has the same length as the previous
          owner's parent (cc) but different text: dd is created even though
          cc has the same length

root.zone: apex "." with a delegation and an implicit parent chain
(a.b.test.), pinning where the parent chain stops at the root.
