add lib versioning

[cakester]

Checklist

GitHub

• I've given this PR a concise, self-descriptive, and meaningful title
• I've linked relevant issues in the PR body
• I've applied the relevant labels to this PR
• I've assigned a reviewer

PR contents

• I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
• I've added relevant tests for my contribution
• I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

Linked issues

ivadomed#501

[cakester]

ideally, i think all >= should be ~= on the safe side

[dyt811]

Good suggestion. I think this would be a very valid issue to bring up as potentially first issue. There MAY have been a reason but I concur with your assessment that it is usually safer to ~= whenever possible. ADS had some FIELD days with their conda environment management process (axondeepseg/axondeepseg#452 and axondeepseg/axondeepseg#484). We might eventually leverage conda at IvadoMed too but that is another discussion. So far, there appear to not be strong need... but that PyTorch requirement... may pose problems down the road. We will keep an eye out.

A minor feedback is to make sure use complete English sentence when interacting with IvadoMed developers. Also... everything you write today WILL be remembered by GitHub for decades to come, so make sure to make them count professionally and impressive over the years.

[cakester]

note the versions are gotten from https://github.com/ivadomed/ivadomed/runs/2181168099?check_suite_focus=true, not pip freeze, since some of the newer versions ci couldn't find

[dyt811]

Be mindful this doesn't get pushed to the main repo. I know you added this to test it here.
Also, for the branch name, please ensure you follow what others have done in terms of branch name see below, with prefix for addressing specific issues if relevant.

[dyt811]

Rock and roll, all good to go. 🚀

[dyt811]

Don't forget to properly Squash and Merge with the appropriate commit messages summarizing everything.

[dyt811]

Also, as a general feedback for commit messages, feel free to go into a bit more details/contexts and references if needed. Usually, if you are not sure you are being verbose or being too brief compare to what is expected of you, lean cautiously towards the verbose side to ensure the communication is extra clear.

[dyt811]

Also, for the real PRs to IvadoMed, make sure you checkmark all the relevant tasks completed from the prompt. You can check mark it after PR issued but best to do it at issue time via [x].