Automatic version update

[MilesF25]

When creating a pull request to add a new feature or alter an existing one,
there are some important elements to include to help our team review and process it more efficiently.

1. Make sure the title is descriptive of what the PR includes. Don't mention issue names/numbers; save that for the description.
   Automating push to PyPi.

2. List the names of those who contributed to the project.
   @VitalJoseph , @KellerLiptrap , @MilesF25 , @Poiuy7312, @boulais01

3. Link the issue the pull request is meant to fix/resolve.
   Automate Version Updates For PyPi #80

4. Describe the contents and goal of the pull request.

The goal is to be able to automate pushing to PyPi

7. Will coverage be maintained/increased?
   Maintained
8. What operating systems has this been tested on? How were these tests conducted?
   None
9. Include a code block and/or screenshots displaying the functionality of your feature, if applicable/possible.

Mark as a draft until it is ready to begin the reviewing process, then tag our Lead Software Architect, Lauren Nevill,
our Principal Software Engineer, Bergas Batara, and our Founding Engineer, Gregory Kapfhammer
when you mark it as ready for review.

[AidanNeeson]

I'm not entirely sure how twine works when it comes to building a package, I cannot seem to locate where it is capturing all of the projects dependencies. I would much rather an approach that uses poetry the tool we are already using. There are commands that are a part of poetry that can assist with this issue, I would recommend looking there. For example, the command poetry version will bump the version number in the toml to a specified number.

[AidanNeeson]

This makes the workflow a lot simpler. Extra steps could be taken to see consistency with the version number listed in the toml and what is on PyPI, but I think this is a good first step at making sure releases can be done consistently.

[Poiuy7312]

Think this looks good