feat: core replay protection

[pedrouid]

Description

This introduces replay protection for each typed enveloped based on the topic

Type of change

• Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

THIS IS STILL MISSING TESTING!

Checklist

• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[paulmillr]

@pedrouid can you check out security improvement issue instead of ignoring it? #3084

[pedrouid]

@pedrouid can you check out security improvement issue instead of ignoring it? #3084

@paulmillr please do not comment on unrelated PRs to elevate the awareness of another issue

This type of commentary is unproductive so please see my response on #3084