Update bundle download API to align with model zoo changes

[yiheng-wang-nv]

The bundle hosting change is that any new bundles/versions will be hosted in Hugging Face.
take maisi_ct_generative for example, it's v0.4.6 is in:
https://api.ngc.nvidia.com/v2/models/nvidia/monaihosting/maisi_ct_generative/versions/0.4.6/files/maisi_ct_generative_v0.4.6.zip
it's latest v1.0.0 is in:
https://huggingface.co/MONAI/maisi_ct_generative/tree/1.0.0

Therefore, MONAI bundle download API should also be updated. For each bundle (each version), the API should be able to download not matter which host it is on. To enable it, we should define the priority of download: NGC or Hugging Face, which host should be accessed first?

Currently, most of the bundles (most of the versions) are in NGC, and only a few of them in Hugging Face, but in the future, new versions will all be in Hugging Face.

My suggestion is that we can prepare a new version for each bundle, to ensure the latest versions are all in Hugging Face. In the API side, let the program try to access to Hugging Face first.

Hi @Nic-Ma @ericspod @KumoLiu , could you help to give some suggestions?

Related model zoo PR: related model zoo changes: Project-MONAI/model-zoo#735

[yiheng-wang-nv]

After having updated download API, we should also update model zoo's weekly tests accordingly

[yiheng-wang-nv]

bundle changes will be tracked in: Project-MONAI/model-zoo#739

[mingxin-zheng]

One benefit I see is that the management of bundle files will be more transparent (not replying on internal NGC storage)

[mingxin-zheng]

Hi @yiheng-wang-nv , will the file on huggingface be a zipped package, or folder of files?

[yiheng-wang-nv]

Hi @yiheng-wang-nv , will the file on huggingface be a zipped package, or folder of files?

Hi @mingxin-zheng , a huggingface model can be considered as a git repo, for example: https://huggingface.co/MONAI/brats_mri_segmentation/tree/main
download it will get a folder of all its files.