refactor(progress): generic progress tracking

[shizhMSFT]

This PR is an implementation of oras-project/oras-go#839.

The goal is to refactor the core code of progress reporting from the oras CLI code base in order to put it into oras-go for others to implement their own progress reporting method.

The refactored code is in the internal/progress package.

[github-actions]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[codecov]

Codecov Report

Attention: Patch coverage is 82.09607% with 41 lines in your changes missing coverage. Please review.

Project coverage is 84.23%. Comparing base (da1daf0) to head (8ca452b).

Files with missing lines	Patch %	Lines
cmd/oras/internal/display/status/track/target.go	48.27%	10 Missing and 5 partials ⚠️
cmd/oras/root/blob/fetch.go	0.00%	4 Missing and 2 partials ⚠️
...md/oras/internal/display/status/progress/status.go	87.50%	5 Missing ⚠️
...oras/internal/display/status/progress/messenger.go	82.60%	3 Missing and 1 partial ⚠️
cmd/oras/root/blob/push.go	20.00%	2 Missing and 2 partials ⚠️
internal/progress/tracker.go	94.28%	3 Missing and 1 partial ⚠️
cmd/oras/internal/display/status/tty.go	90.32%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1524      +/-   ##
==========================================
- Coverage   84.41%   84.23%   -0.19%     
==========================================
  Files         120      121       +1     
  Lines        5460     5568     +108     
==========================================
+ Hits         4609     4690      +81     
- Misses        604      625      +21     
- Partials      247      253       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[shizhMSFT]

Now we have a failure mark on error:

[Wwwsylvia]

Built the code and tested a little bit. Got "panic: send on closed channel" error when running oras push localhost:5000/test:v1 foo.

[Wwwsylvia]

Just a note: This is a bit tricky, is "mounted" a "restored" the same idea in the pull context? If so, wondering if there is a better prompt than "restored".

[shizhMSFT]

The StateMounted is reused for PullPromptRestored given the context of Pull.

[Wwwsylvia]

Yeah I understand the purpose. Just wondering if the prompt "restored" can just be called "mounted".

[shizhMSFT]

It is not very clear what "mounted" means on a file system as we are not doing hard link or making something magic similar to copy-on-write filesystem.

[shizhMSFT]

Got "panic: send on closed channel" error when running

A ha. This PR indeed requires further refactoring.