Standardized CLI options

[scap3yvt]

Fixes #849

Proposed Changes

• updated cli options to standardize them

Checklist

• [x] CONTRIBUTING guide has been followed.
• [x] PR is based on the current GaNDLF master .
• [x] Non-breaking change (does not break existing functionality): provide as many details as possible for any breaking change.
• [x] Function/class source code documentation added/updated (ensure typing is used to provide type hints, including and not limited to using Optional if a variable has a pre-defined value).
• [x] Code has been blacked for style consistency and linting.
• [x] If applicable, version information has been updated in GANDLF/version.py.
• [x] If adding a git submodule, add to list of exceptions for black styling in pyproject.toml file.
• [x] Usage documentation has been updated, if appropriate.
• [x] Tests added or modified to cover the changes; if coverage is reduced, please give explanation.
• [x] If customized dependency installation is required (i.e., a separate pip install step is needed for PR to be functional), please ensure it is reflected in all the files that control the CI, namely: python-test.yml, and all docker files [1,2,3].

[github-actions[bot]]

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

[sarthakpati]

@hasan7n @aristizabal95 @VukW - do you have any idea why the MLCube deploy test is failing?

[VukW]

Hi @sarthakpati! this PR would have a lot of essential conflicts while merging with https://github.com/mlcommons/GaNDLF/pull/845 as all the scripts are refactored heavily while moving to new CLI API. How urgent are these fixes?

• If we want to fix this right now (or, just, before releasing 0.1.0), then may I ask you to fix just a parameters names? It would be much easier for me to solve conflicts later + all the logic around argparse (say, checking if param is required) would be not used soon.
• Or maybe we can release 0.1.0 firstly? And standartize param names later?
• Or, if the question only about param names but not param behavior, we may fix it directly in https://github.com/mlcommons/GaNDLF/pull/845 ?

[sarthakpati]

@VukW: I agree - this PR is not critical, and let's change this to get merged into #845 instead, since this is basically only about standardizing param names. Do you think you can help @scap3yvt with this?

IMO, same goes for #852 - thoughts?

[VukW]

@sarthakpati yes, sure, I can help, though not sure how exactly

But it seems to me that it may be easier to start a new branch based on https://github.com/mlcommons/GaNDLF/pull/845 rather than merge conflicts. @scap3yvt what do you think? Can you take #845 as base and add fixes & improvements over it? Or do you need my help for it? If any, feel free to ping me, let's solve this together

[VukW]

@sarthakpati concerning #852 - that PR is not meant to be merged, I use it for testing & debugging MLCube CI test that behave in strange way for me

[sarthakpati]

This has been superseded by #853