Establish versioning convention

[Leengit]

This GitHub issue is to provide a forum to discuss: to maintain maximum compatibility with 3D Slicer conventions, how and when do we want to update VPAW's application version numbers and GitHub releases and tags?

[ebrahimebrahim]

I think it makes sense to do a release whenever we complete a chunk of requirements and we are ready to share a version of the application with the rest of the research group. We can do one now, if we are done testing that built packages work on both linux and windows.

Here's how I imagine releasing might work:

• create a commit on main that updates the version number here
• add a git tag of the version number onto that commit
• build packages for linux and windows
• create a release on this repo in github. the release will point to the tag and we can upload the built packages to it.

There are other workflows like having a release branch or having a branch for every release, but I think those are overkill for this application.