Design automated publishing

[theory]

Design a pattern for automated building and publishing Trunk/OCI packages on some trigger. A Git merge is adequate for now, but we should plan to move to a more queue or webhook-based trigger in the future (See Interactions for details).

Even still, we need to support a variety of platforms and architectures in the future, and it will change over time. Perhaps there's some way to have:

• A registry of trusted build nodes
• A way to notify those nodes of new build needs
• A way to track responses from those nodes, ultimately including packages to release

In the short term, imagine this:

• A merge into the Design source registry repository with metadata patches to merge #45 repo triggers a workflow that notifies all registered nodes (or some service that does so)
• Each node gets the request, ACKs it, performs the build, and submits the result…somewhere
• That somewhere aggregates the OCI packages and publishes them with proper image index and annotations

There's a lot to balance here in terms of MVP, trusted relationships, and long-term design goals.