Nsec optimi2reb

Slight re-factoring of code for NSEC/NSEC3 creation and updates.

Previously, all NSEC(3) records were first put into a changeset, and later the changeset applied on zone update.

Now, the generated records are put immediately into the zone update structure.

This change itself has no positive impact on performance (rather negative (?)), but simplifies the code and enables further re-designing of whole signing process (getting rid of changesets; doing things more incremental; incremental adjusting).

changed milestone to %2.9

added discussion research labels

added 15 commits

• 7230dfe3...a3ee068e - 7 commits from branch master
• b9ed938b - nsec3: cleanup code before re-designing it
• 3f172805 - nsec3: avoid using extra changesets for signing nsec chain
• 1eee1168 - nsec/nsec3: avoid using extra changeset for fixing chain
• 95693fa3 - nsec/nsec3: simplified code for fixing chain
• dcd4521c - nsec3: avoid extra changeset when creating nsec3 chain
• a138b6b8 - nsec3: get rid of using extra changeset completely
• 29972847 - dnssec/nsec_update: bugfix: removed code removing what had been removed
• 71aa73e7 - bugfix: assertion no longer valid

Compare with previous version

merged

mentioned in commit 6b216cf0