Expose missing sender session history FFI methods

[arminsabouri]

Foreign languages should have access to the send session status after replayling the session event log.

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.

[arminsabouri]

is inner idiomatic? or should it just be pub struct SenderSessionStatus(payjoin::send::v2::SessionStatus)

[benalleng]

There doesn't seem to be a perfectly consistent approach that we take, SenderSessionEvent has a tuple struct while SenderSessionOutcome has named fields, this seems fine imo

[spacebear21]

I prefer tuple struct where there's only one inner value, but we can make this consistent in a follow-up.

[coveralls]

Pull Request Test Coverage Report for Build 18224907273

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 84.237%

---

Totals
Change from base Build 18224113546:	0.0%
Covered Lines:	8962
Relevant Lines:	10639

---

💛 - Coveralls

[benalleng]

ack, the different SenderSession Structs in the ffi already accept a variety of tuple vs named fields, it seems fine for this to be this way unless we want to definitively settle on one or the other.

[arminsabouri]

ack, the different SenderSession Structs in the ffi already accept a variety of tuple vs named fields, it seems fine for this to be this way unless we want to definitively settle on one or the other.

You are right. The other exports just wrap around the rust-payjoin type. I think thats better bc the foreign language won't have some class with a inner field.

[spacebear21]

ACK, receive needs the same treatment (I'll open a PR).