Made test for versioning system.

[MicahGale]

Description

This was meant to be a bug fix for #386. However, since this bug I have been unable to replicate the error in CI, or even on the machine had initially had the error.

Nonetheless I saw some opportunities for making this version system more robust.

Background on version system.

How versions were determined changed with #336.
At this point we moved to setuptools-scm, and the version is never hard coded into a git tracked file.
Rather the tool uses git tag and git commits to determine the current/next version.
This is expensive to do so it is only done when python -m build is ran.
At this point the version number is calculated and saved to montepy/_version.py.
It is also possible to figure out the version number by importing setuptools_scm.

To determine the version montepy does the following:

1. tries to import _version.py and use that.
2. If that fails it tries to import setuptools_scm
3. If that fails too, it falls back to Undefined.

Improvements

1. Improved coverage by testing all branches of this logic in tests/test_version.py. This test is rather jank because it has intentionally unload setuptools_scm and montepy so it can force it re-import multiple times.
2. Improved CI to always generate a test report even if the tests failed.
3. Added a catch for a LookupError so if setuptools_scm fails for some reason the user will get Undefined.

Fixes #386

Checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation (if applicable)
• I have added tests that prove my fix is effective or that my feature works (if applicable)

[coveralls]

Pull Request Test Coverage Report for Build 8211674948

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.1%) to 98.261%

---

Totals
Change from base Build 8159050757:	0.1%
Covered Lines:	5762
Relevant Lines:	5864

---

💛 - Coveralls