Upgrade to distribution (registry) v3 alpha

[AaronDewes]

Comprehensive Summary of your change

This includes all the benefits of the v3 distribution, but also all breaking changes.

Most notably, Image Manifest v2 Schema v1 support has been dropped, as well as the oss and swift storage drivers.

Currently, this still relies on v2's github.com/docker/distribution through indirect dependencies.

This PR is a draft because distribution v3 isn't stable yet. However, I am sucessfully running Harbor of this branch.

Issue being fixed

None

Please indicate you've done the following:

• Well Written Title and Summary of the PR
• Label the PR as needed. "release-note/ignore-for-release, release-note/new-feature, release-note/update, release-note/enhancement, release-note/community, release-note/breaking-change, release-note/docs, release-note/infra, release-note/deprecation"
• Accepted the DCO. Commits without the DCO will delay acceptance.
• Made sure tests are passing and test coverage is added if needed.
• Considered the docs impact and opened a new docs issue or PR with docs changes if needed in website repository.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (9e5efc9) 70.63% compared to head (55de925) 45.25%.

Additional details and impacted files

@@                    Coverage Diff                    @@
##           distribution_v3_test   #19784       +/-   ##
=========================================================
- Coverage                 70.63%   45.25%   -25.39%     
=========================================================
  Files                       747      244      -503     
  Lines                     95833    13332    -82501     
  Branches                      0     2720     +2720     
=========================================================
- Hits                      67696     6033    -61663     
+ Misses                    24469     6998    -17471     
+ Partials                   3668      301     -3367     

Flag	Coverage Δ
unittests	45.25% <100.00%> (-25.39%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...ponents/label-selector/label-selector.component.ts	68.18% <100.00%> (ø)

... and 989 files with indirect coverage changes

[wy65701436]

thanks @AaronDewes , I'm considering using a separate branch for your changes. This approach allows us to conduct thorough testing to prevent any potential regressions.

[MinerYang]

Hi @AaronDewes ,

Thanks for your contribution! Would you mind changing the merge branch from main to distribution_v3_test. We would like to do regression test based on this branch

[AaronDewes]

Hi @AaronDewes ,

Thanks for your contribution! Would you mind changing the merge branch from main to distribution_v3_test. We would like to do regression test based on this branch

Sure, I'll also rebase this later.

[AaronDewes]

The files that depend on "github.com/docker/distribution/registry/client/auth/challenge" still need refactoring to drop that dependency; but I can do that in a separate PR if you already want to start testing this.

[wy65701436]

As for the separate branch, we can proceed by merging the PR and then focus on regression testing. If any issues are identified during testing, we can address them promptly. Additionally, there may be a need to contribute the changes upstream.

@MinerYang Im OK to merge it if the CI passes, and start the regression testing.

[AaronDewes]

@wy65701436 I fixed the build failures, but DCO fails now after I rebased on master. Can you merge master into distribution_v3_test first, so the DCO bot passes? And the CI requires another approval because I pushed a commit and I'm a first time contributor.

[MinerYang]

Hi @AaronDewes ,
Please help to fix the DCO via git config and amend your commit with -s

[AaronDewes]

@MinerYang My commit is signed off. The problem is that this PR contains commits from master not yet in the distribution_v3_test branch. The commits in master are not from me and not all signed off. You or another project member need to merge master into ``distribution_v3_test`.