Updating version fetching to no longer use pkg_resources

[phargogh]

Using importlib.metadata or importlib_metadata depending on the python version to get version metadata.

Fixes #100

[davemfish]

Hey @phargogh , this begs the question, should we still support python < 3.8? We're no longer testing against it, though pyproject.toml allows >= 3.6. And Python 3.6 & 3.7 have reached end-of-life. Thoughts?

Also, this question can definitely be the topic of a different issue/PR and we can call this one good as-is.

[phargogh]

Thanks @davemfish ! I was wondering about that as well, and I think it'd be better to push that to another issue (#102) for consideration. Syntactically, I believe python 3.6 and 3.7 should still work, but the question of whether we should be supporting these versions is different. I left things alone because of the syntactic angle rather than the maintenance angle.

[davemfish]

Thanks @davemfish ! I was wondering about that as well, and I think it'd be better to push that to another issue (#102) for consideration. Syntactically, I believe python 3.6 and 3.7 should still work, but the question of whether we should be supporting these versions is different. I left things alone because of the syntactic angle rather than the maintenance angle.

Okay great!