Figure out how to deal with various package versioning mismatches #1962
Description
The "delphi-utils" package in this repo has its own bump2version config and its two version references seem to be in sync with that (.bumpversion.cfg, __init__.py, setup.py). This is good because it is an actual package used in places external to this repo. delphi-utils also has its own specific and distinct directives in the create and publish release github actions.
Each individual indicator in this repository has its own unique packaging, but all of their version numberings are in sync with the others. It probably isnt a huge deal because they are all mostly (only?) used internally. Its ultimately due to the fact that they currently share a .bumpversion.cfg, and they are all covered symmetrically by the github action definitions linked in the previous paragraph. You can easily see with a gh code search that they share the same current_version = ... in their respective version.cfg files. HOWEVER, those version numbers match neither their setup.py nor __init__.py files with any consistency. We should make them all match and appropriately add them to the bumpversion configuration for sanity's sake.
Also consider breaking up the indicators into their own independent version paths, instead of having them all match each other.