Updated the metadata for all models, focused on name, description, and task for Model Zoo website improvements.

[zephyrie]

Description

Updated the metadata for all models, focused on name, description, and task for Model Zoo website improvements.

Status

Ready/Work in progress/Hold

Please ensure all the checkboxes:

• [] Codeformat tests passed locally by running ./runtests.sh --codeformat.
• In-line docstrings updated.
• Update version and changelog in metadata.json if changing an existing bundle.
• Please ensure the naming rules in config files meet our requirements (please refer to: CONTRIBUTING.md).
• Ensure versions of packages such as monai, pytorch and numpy are correct in metadata.json.
• Descriptions should be consistent with the content, such as eval_metrics of the provided weights and TorchScript modules.
• Files larger than 25MB are excluded and replaced by providing download links in large_file.yml.
• Avoid using path that contains personal information within config files (such as use /home/your_name/ for "bundle_root").

[zephyrie]

@yiheng-wang-nv, there were some issues with ./runtests.sh --codeformat, but they were in code I didn't touch so I left them alone for now. Everything else looked fine.

[zephyrie]

@ericspod, I found 7 instances of the 'authors' key issue that I've fixed now.

[ericspod]

Looks good to me, thanks!

[yiheng-wang-nv]

/build

[yiheng-wang-nv]

/build

[yiheng-wang-nv]

/build

[yiheng-wang-nv]

The current cpu check error is due to github's machine does not have enough spaces (this PR changes multiple bundles, thus requires large spaces). Since the blossom machine based tests are successful, I will temporarily modify the PR merge requirement, and merge it first. cc @ericspod

[ericspod]

The current cpu check error is due to github's machine does not have enough spaces (this PR changes multiple bundles, thus requires large spaces). Since the blossom machine based tests are successful, I will temporarily modify the PR merge requirement, and merge it first. cc @ericspod

This was the only way forward at the moment so it's fine. I would suggest we need to consider here, and in other repos, how to formulate test rules to be skipped if documentation files alone are changed in which case code doesn't need testing.