[forwardport v2.9] Git Clone Error: Empty git-upload-pack-given using SSH or HTTPS to Azure DevOps Repos

[rancherbot]

This is a forwardport issue for #2043, automatically created via GitHub Actions workflow initiated by @raulcabello

Original issue body:

Rancher Server Setup

• Rancher version: 2.8

Information about the Cluster

• Kubernetes version: 1.25.15
• Cluster Type: Local
• Hosted: AKS

Describe the bug
Rancher Fleet jobs report: "Error cloning repository: empty git-upload-pack given" when connecting to a previously working Git Repo in Azure DevOps Repos using both SSH and HTTPS authentication.

To Reproduce

• Upgraded Rancher 2.7.9 to Rancher 2.8

Result

• Git Repos are stuck in the status Updating Git

Expected Result

• Git Repos sync like they did in 2.7.9

Screenshots

[raulcabello]

QA Template

Solution

Azure DevOps requires capabilities multi_ack / multi_ack_detailed, which are not fully implemented and by default are included in transport.UnsupportedCapabilities. transport.UnsupportedCapabilities have been changed to support that.

Testing

• Test GitRepos are deployed successfully for git repositories hosted in Azure DevOps.
• All the other git providers should keep working fine (e.g. github, bitbucket, gitlab)

Additional Info

• This fix just works on private repositories. We need to wait for go-git to implement v2 protocol in order to support public repositories

[mmartin24]

QA test report

We currently test daily app deployment with private repos (Azure, Github, Bitbucket, Gitlab) in rancher v2.7-head, v2.8-head and v2.9-head.

• Check deployment of nginx app over Azure private repo using both ssh and http auth on Rancher v2.9-head (v2.9-c9be13b09329bbee60a5f6419d500198f83c44d1-head ) here with fleet:104.0.0+up0.10.0-rc.11 passing using single node k3s cluster v1.28.8+k3s1
  

• Checked deployment over 2.7-head and 2.8-head and then upgraded to 2.9-head and worked as well: