Since Curl 7.83.0 http redirect on mirrors strips out authentication headers

Issue Summary

Since https://curl.se/docs/CVE-2022-27776.html was resolved in Curl 7.83.0 header information is not stripped out on redirect. This causes pushes to mirror nodes to lose their authentication header when using a token and the request to ask for basic auth details.

Due to this being driven from the Curl version on the client side it impacts all versions of Bitbucket.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create a token on a repo with write permissions
2. Push to that repo using `git -c http.extraHeader='Authorization: Bearer <token>' push <miror base url>/mirror/scm/<project>/<repo>.git
   `

Expected Results

The request should be sent to the upstream with authentication

Actual Results

1. The request should be redirected to the upstream without authentication

Workaround

-Downgrade to curl 7.82.0 or

-Use ssh authentication or