Replace wget on Windows with built-in curl

[paulober]

Since Build 17063 (Win 10) Windows includes a curl distribution. This PR replaces the usage of wget with the built-in curl executable.

See https://curl.se/windows/microsoft.html for reference.

@tdewey-rpi @will-v-pi

[stephanosio]

One of the reasons why wget was chosen over curl initially was that it has a much nicer progress bar showing file name, download size, download speed and remaining time, whereas curl has a very basic and ugly progress bar that provides none of the aforementioned details.

Given that we recommend and depend on wget for many other things in the documentation and wget can be easily installed using winget alongside many other components that are not available on Windows, I am not convinced that this is a necessary change.

[paulober]

One of the reasons why wget was chosen over curl initially was that it has a much nicer progress bar showing file name, download size, download speed and remaining time, whereas curl has a very basic and ugly progress bar that provides none of the aforementioned details.

Given that we recommend and depend on wget for many other things in the documentation and wget can be easily installed using winget alongside many other components that are not available on Windows, I am not convinced that this is a necessary change.

Understood. The thing is if you want to integrate zephyr setup into your tooling you have other more convenient options to download the rest so then wget would only be required to run this script which is really not necessary. So what about keeping wget the default and give an option via flag / fallback to use curl?

[paulober]

If you accept this solution I would also like to add it as option / fallback to macOS as it has also curl installed by default and wget would need to be installed separately.

[stephanosio]

Understood. The thing is if you want to integrate zephyr setup into your tooling you have other more convenient options to download the rest so then wget would only be required to run this script which is really not necessary. So what about keeping wget the default and give an option via flag / fallback to use curl?

7z, another utility not available by default on Windows, will need to be installed or provided in some way for this script to run; so, I do not really understand the desire to use curl on the basis that it is already available on Windows -- the script will not be able to run on vanilla Windows anyway.

The question is: why is it so hard to provide wget as with 7z, which you will need to provide anyway, in your tooling?