Persist private preferences to keystore

[rygine]

Summary

This PR adds caching of private preferences to the JS SDK.

• Upgraded @xmtp/proto for encoding of a private preferences action map
• Added a private preferences store to manage persisting of actions
• Added new methods to InMemoryKeystore to interact with the private preferences store
• Refactored Contacts class to use the private preferences store
• Removed deprecated/unused lastConsentListEntryTimestamp method from Contacts class

Notes

• The use of for loops rather than for..of is intentional as it's more performant with a large number of iterations.
• The persistence of private preferences relies on the existing persistConversations option. I think they should be tied together and having a separate option would create unnecessary complexity.
• The actions are key'd by their timestamp, which should be unique. The use of their timestamp is necessary in order to process them in the proper order. While it's technically possible to have 2 separate actions published with the same timestamp, it's not something we should worry about under normal circumstances. In the case that there are 2 actions with the same timestamp, the first one returned by the network will be the one used. Any subsequent actions with a duplicate timestamp will be ignored.

[changeset-bot]

🦋 Changeset detected

Latest commit: dafd1e5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@xmtp/xmtp-js	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cloudflare-workers-and-pages]

Deploying xmtp-js-docs with    Cloudflare Pages

Latest commit:	dafd1e5
Status:	✅  Deploy successful!
Preview URL:	https://3b5f3a9d.xmtp-js.pages.dev
Branch Preview URL:	https://rygine-persist-consent.xmtp-js.pages.dev

View logs