Add MLS Service

[neekolas]

Summary

• Adds a MLS delivery service, with a moderately thought through API spec. Subject to change, but I want to get something in to scaffold the service, even if some of the endpoints wind up changing.
• Adds a few wrapper types for the message formats that will be published to the network

[neekolas]

Realized that the new Protobuf formatter doesn't necessarily split lines (for example, for long RPC definitions)

[neekolas]

I just skipped right over V2 and went straight to V3 for naming consistency with other V3 protos

[richardhuaaa]

Happy to get something in and iterate.

One idea I'd like to plant here is if we are able to make any of these endpoints less MLS-specific? For example, by introducing a generic OrderedTopic concept, or a generic SingleUseTopic?

[neekolas]

One idea I'd like to plant here is if we are able to make any of these endpoints less MLS-specific? For example, by introducing a generic OrderedTopic concept, or a generic SingleUseTopic?

I'm open to ordered topics. I'd like to get a better understanding of what you'd want a SingleUseTopic to do.

Even with that, I think the PublishToGroup is going to be pretty MLS-specific until we have a better commit resolution strategy. That one requires not just ordering, but also rejection of messages from past epochs so that the client can refresh their state and retry the request.

[richardhuaaa]

Just spitballing, a SingleUseTopic deletes payloads as they are read. An OrderedTopic requires payloads to have two fields, currentEpoch and nextEpoch, and publishes fail if currentEpoch doesn't match the current epoch. I say this with low confidence, I think you're deeper into what the actual validation logic would be than I am

[github-actions]

🎉 This PR is included in version 3.30.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀