Assert reply_key for RetrievedOriginalPayload

[benalleng]

Fixes the mutant in #1151

Pull Request Checklist

Please confirm the following before requesting review:

• I have disclosed my use of
  AI
  in the body of this PR.
• I have read CONTRIBUTING.md and rebased my branch to produce hygienic commits.

[coveralls]

Pull Request Test Coverage Report for Build 18288262677

Details

• 6 of 6 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.007%) to 84.217%

---

Totals
Change from base Build 18286617728:	0.007%
Covered Lines:	8954
Relevant Lines:	10632

---

💛 - Coveralls

[spacebear21]

Suggested change

	SessionHistory { events: events.clone() }.session_context().reply_key,
	SessionHistory::new(events.clone()).session_context().reply_key,

[spacebear21]

I wonder if it might be less hacky to test for the presence of the reply_key in run_session_history_test? It's a bit of a special case because it's session_context() is a private function but if the goal is to assert that a reply_key is present on sessions that retrieved the original payload I feel like the tests should be more systematic about that.

[benalleng]

Ok, thats fair, I just created a match block in run_session_history_test that checks if there is a RetrievedOriginalProposal event and checks for the reply_key then

[spacebear21]

ACK 2bb3e72