Change Helm upload success to 202 Accepted

What does this MR do?

From discussion #338412 (comment 660766297)

⚠ Marking as draft and currently on workflowblocked because this is a breaking change for helm-push plugin and gitlabracadabra and we will have to wait for Gitlab 15.0 16.0.

The following should be merged and released before:

• https://github.com/chartmuseum/helm-push/pull/107
  • Merged
  • Released in helm-push v0.10.0 2021-10-04
  • few month have passed ...
• gitlabracadabra/gitlabracadabra!190 (merged)
  • Merged
  • Released in 1.3.0 2021-11-10
  • few month have passed ...

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team