install-badge-dev-env should use git clone https:// instead of git clone git://

[TonyLHansen]

Many systems are behind firewalls that make it difficult to use "git clone" with git:// URLs, whereas https:// URLs will work fine with the proper proxies. The few git clone statements in install-badge-dev-env should use git clone https instead of git clone git://

[TonyLHansen]

In addition, github.com appears to no longer support the git:// protocol:

https://github.blog/2021-09-01-improving-git-protocol-security-github/

No more unauthenticated Git

On the Git protocol side, unencrypted git:// offers no integrity or authentication, making it subject to tampering. We expect very few people are still using this protocol, especially given that you can’t push (it’s read-only on GitHub). We’ll be disabling support for this protocol.