chore: add reference details to registry errors

[sajayantony]

What this PR does / why we need it:
The errors from the oras CLI does not show the actual value that was provided.
The following PR updates the erros to include the actual user provided reference here -

$ oras copy test someotherregistry.azurecr.ui/myimage:v1
Error: "test": invalid reference: missing registry or repository

$ oras copy test.com someotherregistry.azurecr.ui/myimage:v1
Error: "test.com": invalid reference: missing registry or repository

$ oras copy test.com/test someotherregistry.azurecr.ui/myimage:v1
Error: "test.com/test": no tag or digest when expecting <name:tag|name@digest>

$ oras copy test.com/test: someotherregistry.azurecr.ui/myimage:v1
Error: "test.com/test:": no tag or digest when expecting <name:tag|name@digest>

$ oras copy test.com/test@ someotherregistry.azurecr.ui/myimage:v1
Error: "test.com/test@": no tag or digest when expecting <name:tag|name@digest>

$ oras copy test.com/test:() someotherregistry.azurecr.ui/myimage:v1
Error: "test.com/test:()": invalid reference: invalid tag "()"

$ oras copy test.com/test@invalid someotherregistry.azurecr.ui/myimage:v1
Error: "test.com/test@invalid": invalid reference: invalid digest "invalid": invalid checksum digest format

[codecov-commenter]

Codecov Report

Merging #1152 (1a689ea) into main (f2ed16a) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

@@            Coverage Diff             @@
##             main    #1152      +/-   ##
==========================================
- Coverage   79.47%   79.45%   -0.02%     
==========================================
  Files          65       65              
  Lines        3493     3495       +2     
==========================================
+ Hits         2776     2777       +1     
- Misses        506      507       +1     
  Partials      211      211              

Files	Coverage Δ
cmd/oras/internal/errors/errors.go	100.00% <100.00%> (ø)
cmd/oras/internal/option/remote.go	78.09% <100.00%> (-0.28%)	⬇️
cmd/oras/internal/option/target.go	84.69% <100.00%> (ø)
cmd/oras/root/manifest/delete.go	83.54% <100.00%> (ø)

[qweeah]

lgtm

[sajayantony]

Thanks @shizhMSFT @qweeah

[vsoch]

Any possibility to get a develop or branch named container build here? I just ran into the (previous) ambiguous error and this would be very helpful!

In the meantime I'll do a custom build, but would be great to have this tag ready to go.

[qweeah]

@vsoch You may try go install oras.land/oras/cmd/oras@main if you have g1.21.x installed.

[vsoch]

@qweeah it's for an operator sidecar that (ideally) doesn't require minimal setup. I am suggesting building a latest tag (that reflects the current main branch) so users always have access to the latest (and not the last release, which can be months old).

[qweeah]

Agree, adding a container can be a good start. The container can be built when merging PR into main branch Not sure about the tag naming, maybe main is better than latest? @FeynmanZhou

[vsoch]

Perhaps a develop or main (branch) tag would make sense? It should indicate “this is not a production container there might be bugs use at your own risk!”

[sajayantony]

@qweeah is there an issue for pushing an updated container on merge or maybe daily?

[qweeah]

@qweeah is there an issue for pushing an updated container on merge or maybe daily?

I will create one.

[FeynmanZhou]

Any possibility to get a develop or branch named container build here? I just ran into the (previous) ambiguous error and this would be very helpful!

In the meantime I'll do a custom build, but would be great to have this tag ready to go.

@vsoch Are you expecting an ORAS image with a latest flag automatically built from the main branch for non-prod environment? Is this issue #1155 meet your expectation?