ci: publish images as gluwa/asc-message-relayer

[DylanVerstraete]

The Docker Hub repo name still lagged the GitHub rename, so images built from asc-message-relayer were being published to gluwa/usc-message-relayer. This points the release workflow (and the README build examples) at gluwa/asc-message-relayer.

The old repo is deliberately left in place with its tags intact — 0.6.0 is what usc-devnet runs right now, and anything else pinned to a published usc- tag keeps pulling. Only new builds move.

Verified before writing this:

• gluwa/asc-message-relayer does not exist on Docker Hub yet (404), so the first push creates it. Docker Hub may create it private.
• That is safe here: the cc3-usc-dev values already reference the gluwa-docker-hub-private imagePullSecret, so the pull works either way. Worth flipping the repo to public afterwards to match the old one (public, 2.5k pulls).
• Workflow YAML parses; no other stale usc-message-relayer refs remain in the repo except the config.example.yaml header comment, which is prose about the binary, not an image ref.

Once merged, the resulting main-<sha> image is what goes onto usc-devnet.

https://claude.ai/code/session_01Kv6y52MHgtgkWmnJhdXbHB

[cursor]

PR Summary

Low Risk
Documentation and CI image repository naming only; no runtime, auth, or protocol logic changes.

Overview
Aligns Docker publishing with the asc-message-relayer GitHub rename by pointing CI and docs at gluwa/asc-message-relayer instead of gluwa/usc-message-relayer.

The release workflow’s IMAGE env var now tags and pushes to the new Hub repo, with comments noting that gluwa/usc-message-relayer is intentionally left alone so existing pins (e.g. 0.6.0) keep working. README Docker examples and the CI publish blurb were updated to match the new image name and tag scheme (main, main-<sha>, v*, latest).

^{Reviewed by Cursor Bugbot for commit cfe6128. Bugbot is set up for automated code reviews on this repo. Configure here.}