When skipCommitsForExpiredKeys is enabled, original commit entries for each of the keys might be getting left behind

[srieteja]

Describe the bug

skipCommitsForExpiredKeys has been implemented (#1660), which skips writing commit entries when deleting expired keys. When enabled, the original commit entry created while creating the key might be left behind.

Previously, when an expired key was deleted the latest commitEntry for that key would be updated to DELETE which is valid. But with this change, the latest commitEntry would indicate CommitOp.UPDATE but the key actually has been deleted.

Expected behaviour

The commitLog should contain accurate and up-to-date details for the status of each key in the Keystore

Possible solutions

• Delete all commitEntries for an expired key when it's being removed from the Keystore.

Additional context

• Although Improve commit log handling for expired (expiresAt has passed) records #1660 has been implemented, this has NOT been enabled yet.
• Also, this only affects the deletion of expired keys. Manual deletion of keys using the delete verb is unaffected.

[srieteja]

Manual testing is being done for this implementation in the linked PR. Carrying it forward to PR95.