Implement replay_event_log_async

[spacebear21]

As we now have AsyncSessionPersister to enable a sync persistence (#1235), we need to be able to replay the event log asynchronously too.

There's still considerable duplication between the replay_events functions on the send and receive sides, but I'm not convinced whether we should refactor further by introducing a SessionEvent trait that both the receive and sender SessionEvent types could both implement (and the same on Receive/SendSession).

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 21076949429

Details

• 228 of 236 (96.61%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.3%) to 83.357%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
payjoin/src/core/receive/v2/session.rs	131	135	97.04%
payjoin/src/core/send/v2/session.rs	97	101	96.04%

Totals
Change from base Build 21044982881:	0.3%
Covered Lines:	9937
Relevant Lines:	11921

---

💛 - Coveralls

[arminsabouri]

cACK be7d040

Just had one question. Otherwise code looks good.

[arminsabouri]

In the previous code if process_event failed we close the session. Is this a regression?

[arminsabouri]

It looks the close was move to the replay_events call side. Is that right?

[spacebear21]

replay_events does no IO so that it can be reused in the async version of replay_event_log. So it just returns an error here and that's handled with a session close in replay_event_log/_async:

    let (receiver, session_events) = match replay_events(logs.map(|e| e.into())) {
        Ok(r) => r,
        Err(e) => {
            persister.close().await.map_err(|ce| {
                InternalReplayError::PersistenceFailure(ImplementationError::new(ce))
            })?;
            return Err(e);
        }
    };

[spacebear21]

I added a second commit that adds test coverage for this scenario to confirm no regression