Provide tooling and documentation for other Kubernetes subproject to publish their packages

Switching to the community infrastructure for building and publishing packages brings a new possibility for other Kubernetes subproject to publish their packages. We should enable projects interested into this by providing tooling, documentation, and guidance.

This should follow up on #3171

/sig release
/area release-eng
/kind feature documentation
/priority important-longterm

Start by reviewing the context in issue #3171 and the community infrastructure referenced there. Identify the tooling, documentation, and guidance needed for other Kubernetes subprojects to publish packages, then confirm that the resulting workflow is usable by an interested subproject.

Written by the indexing model from the issue text.