Drep registration expiration fix

[teodanciu]

Description

Registering a drep at a time when there were dormant epochs results in the drep expiry to be set greater than expected (ppDrepActivity + currentEpoch + vsNumDormantEpochs).

This PR changes this value, by setting the expiration using the same calculation as for UpdateDrep signal, namely: ppDrepActivity + currentEpoch - vsNumDormantEpochs, since the latter value is going to be added to the computation by CERTS,if there are proposals in the transaction.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated
• All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages.
  New section is never added with the code changes. (See RELEASING.md)
• When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
  versioning process.
• The version bounds in .cabal files for all affected packages are updated.
  If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
• Code is formatted with fourmolu (use scripts/fourmolize.sh)
• Cabal files are formatted (use scripts/cabal-format.sh)
• hie.yaml has been updated (use scripts/gen-hie.sh)
• Self-reviewed the diff

[aniketd]

Very nice catch and investigation!

[lehins]

Looks great. Thank you for finding and fixing this issue!