Characterization fixture: the line stored for an implicitly created parent.

example.sec.signed is a NSEC3-signed zone (RSASHA256, 30-day window
2027-01-01 .. 2027-01-31 UTC, NSEC3 algorithm 1, 0 iterations, empty salt)
post-processed by regenerate.sh so that:

  - the b.c.example.sec. TXT and its RRSIG are the last lines of the file, so
    b.c.example.sec. is first created implicitly, as the parent of
    a.b.c.example.sec.;
  - the NSEC3 for b.c.example.sec. and its RRSIG are deleted.

validns then reports "no corresponding NSEC3 found for b.c.example.sec." at
the line of the a.b.c.example.sec. A record that created the name.  The test
pins that line number and the other output of the broken NSEC3 chain, so any
change to how parent names are created must keep reporting the same thing.
The zone is deliberately invalid; it is not a model of a good signed zone.

Test-time used by src/t/test.pl: 1800057600 (2027-01-15 12:00 UTC,
mid-window).  If regenerate.sh is changed to use a different window, update
the -t flag in test.pl accordingly.

To regenerate (requires BIND 9 tools dnssec-keygen, dnssec-signzone,
nsec3hash):

    cd src/t/issues/implicit-parent-line
    ./regenerate.sh

Regenerating changes the keys, the signatures and the NSEC3 hashes.  Afterwards
re-read the line numbers and hash names asserted in src/t/test.pl off the regenerated
example.sec.signed (and the validns output) before committing.
