feat: report the digest of the pushed image
`print_upload_logs` discarded the `aux` entry that ends a push stream, which
carries the digest of what the registry stored. Absence of an error is weaker
evidence of a successful push than presence of a digest, and a caller doing
content-addressed builds has no way to check that the tag points at the image
they built.
`print_upload_logs` now returns the digest and prints it. A pull stream carries
no `aux`, so it returns None there and the caller decides what that means.
`upload_image` says plainly when the registry reported no digest, rather than
printing a success line that implies more than it can support. The push itself
did succeed in that case, so it stays a warning on stderr rather than a failure.