fix: Downgrade ArgoCD traffic to HTTP

[julianxhokaxhiu]

What does this PR do?

This PR fixes the weird port-forwarding termination happening randomly while Tilt is forwarding the traffic on Windows and macOS. The workaround is about downgrading the default traffic from HTTPS to HTTP.

The long version of this issue can be found here: kubernetes/kubernetes#74551 but it triggers a lot more under TLS traffic than on plain HTTP, probably because of how encrypted packets look like and how they go back and forth through the TCP/IP stack.

Additionally, this downgrade will allow end-users to put an HTTPS Load Balancer in front of ArgoCD if required without further issues or configuration requirements.

Related issues

Fixes #18

Checklist before merging

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have checked the contributing document.
• I have checked the existing Pull Requests to see whether someone else has raised a similar idea or question.
• I have added tests that prove my fix is effective or that my feature works.
• I have upgraded the changelog according to the nature of the feature that I am adding to this Pull Request.

[mile-misan]

Just did a test, for 3 mins it worked fine, but it went back to loosing connection. This time error is bit different:

E0119 10:40:02.403098 8424 portforward.go:346] error creating error stream for port 8080 -> 8080: Timeout occurred

[julianxhokaxhiu]

I added one patch that will ensure the connection doesn't timeout at the first second that the service doesn't reply. Increasing it to 5s before hitting a timeout helped to keep the connection constantly alive.

[zimny]

lgtm