Fix issue: harbor 1.7.4 aliyun oss chartmuseum 500

[liqiang-fit2cloud]

Signed-off-by: liqiang-fit2cloud [email protected]

Fix #7288

The issue occurs when using Alibaba OSS for both docker registry and helm chart repository, the endpoint must be specified in the registry_storage_provider_config of harbor.cfg file as the endpoint is mandatory for helm chart, although it's optional for docker registry .
For docker registry the endpoint must contain the bucket name like bucket-name.oss-cn-qingdao-internal.aliyuncs.com, But for helm chart the endpoint must be in the format oss-cn-qingdao-internal.aliyuncs.com which should not contains bucket name.
So if set the endpoint with bucket name docker registry works well but helm chart is not working, if set the endpoint without bucket name docker registry is not working but helm chart works well, it's awkward...

With this PR, the bucket name will be removed from the endpoint for helm chart, both docker registry and helm chart work well.

[coveralls]

Pull Request Test Coverage Report for Build 12739

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 3 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.01%) to 64.55%

---

Files with Coverage Reduction	New Missed Lines	%
src/core/api/repository.go	3	43.62%

Totals
Change from base Build 12733:	-0.01%
Covered Lines:	15967
Relevant Lines:	24736

---

💛 - Coveralls

[ninjadq]

lgtm