🔨 [tuning] Added continuous deployment workflow for PyPI

Type Of Change

[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Any modification in the test cases
[ ] Any modification in the documentation

Checklist:

[x] I have read and followed the contribution guideline.
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change.
[x] All the test cases pass and new modifications in the production code are 100% covered.
[ ] I have made corresponding changes to the documentation.

Related Issue

Closing: #221

Description

This PR adds an automation workflow for automatically deploying later versions of DEM to the Python Package Index when a GitHub Release is issues.

How Has This Been Tested?

While building this code, I have tested it on my own Python packages for proof-of-concept.

Additional info

In order for this workflow to work, you'll have to set PYPI_TOKEN as a GitHub Actions Secret inside the DEM repository, and set it to the value which you'll get after generating a token from https://pypi.org/ for the project.

axem-solutions / dem