Use bumpversion for epidata client

[rzats]

Closes #1431.

Summary:

Updates the versioning in the Python client to the same method used in the JS and R clients. With this method, the version is set to a simple hardcoded string; however, during a new Delphi release, GitHub Actions will run bump2version during the release process and automatically update this string in the code.

This can be replicated in a local environment; the following code should bump the version in the Python client (as well as the .bumpversion.cfg file itself, and 7 other files) to 4.1.21:

python3 -m pip install bump2version
bump2version --current-version 4.1.20 patch

Prerequisites:

• Unless it is a documentation hotfix it should be merged against the dev branch
• Branch is up-to-date with the branch to be merged with, i.e. dev
• Build is successful
• Code is cleaned up and formatted

[melange396]

We are already duplicating the version number twice in this package, once in the __init__.py and once in the setup.py, which is kinda ugly. i would feel better if we could avoid adding a third copy of it. What if we keep the literal in delphi_epidata.py and make https://github.com/cmu-delphi/delphi-epidata/blob/dev/src/client/packaging/pypi/delphi_epidata/__init__.py just look like:

from .delphi_epidata import Epidata, __version__

name = "delphi_epidata"

[melange396]

and dont forget to add to CHANGELOG.md!

[melange396]

to agree with the change in __init__.py:

Suggested change

	_version = "4.1.20"
	__version__ = "4.1.20"

(and then change the other references to this variable as well)

[melange396]

still doesnt match whats in __init__.py!

Suggested change

	_version_ = "4.1.20"
	__version__ = "4.1.20"

the convention is for this to be a "dunder", as seen in the good ol:

if __name__ == '__main__':

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud