Audit serialization trait implementations

[0xZaddyy]

Summary

This PR Audits serialization trait implementations across the codebase to prevent unintentional API exposure and reduce dependencies.

Closes #1147

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 20601614417

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 82.902%

---

Totals
Change from base Build 20575392805:	0.0%
Covered Lines:	9668
Relevant Lines:	11662

---

💛 - Coveralls

[nothingmuch]

I don't know about the serde usage in the ffi stuff and how appropriate it is to remove it for those types

Only commenting about the removal and feature gating in the payjoin crate: i don't think a feature flag for this is desirable because:

• it's one more feature flag, or 2x the feature flag combinations, which are already intractable for us to test
• serialization is required as part of persistence for correct implementation of the protocol, and not all struct fields are pub

so with the feature disabled the crate couldn't be used to write a safe implementation

so i think this dependence on serde in our public api is actually desirable and intended

[spacebear21]

Removing the De/Serialize from payjoin-ffi seems appropriate, they don't do anything there and were probably just copied over unintentionally. Agreed about keeping serde tightly coupled with rust-payjoin for persistence.