Add poetry dynamic versioning and update release process

[d33bs]

Description

This PR adds dynamic versioning changes intended to eventually assist with #19 by adding CytoTable version metadata into Parquet output. The goal is to enable dynamic version capture in both development (git source-based) and published releases (PyPI, etc), meaning data created by CytoTable from either path would be accurately versioned (enhancing data provenance / lineage understanding for audiences). While dunamai and __version__ aren't necessarily required yet, I intend to use them with further changes towards #19 and thought early discussion / review / visibility might assist.

As part of this I had to update the release process and tried to practice DRY better with GitHub Actions during the process. I also updated the pre-commit check versions as a general act of good source-keeping.

What is the nature of your change?

• Bug fix (fixes an issue).
• Enhancement (adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• This change requires a documentation update.

Checklist

Please ensure that all boxes are checked before indicating that a pull request is ready for review.

• I have read the CONTRIBUTING.md guidelines.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• New and existing unit tests pass locally with my changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have deleted all non-relevant text in this pull request template.

[kenibrewer]

Nice to see this tooling brought to cytotable too! LGTM

[d33bs]

Thank you @kenibrewer ! Definitely inspired by your great work in Pycytominer! 🙂

[d33bs]

@kenibrewer , thanks again for your review here! Would you like to be a CytoTable maintainer? I feel that the project could benefit from your insights. If so, let me know and I'll send along an invite.

[kenibrewer]

@d33bs Sure! I already watch this repo so I can stay aware of the upstream changes that might impact pycytominer. I'd be happy to provide feedback and insights more formally.

[d33bs]

Thanks a bunch @kenibrewer - added!