Relax api version pinning to allow patch versions
I propose to relax a bit the version pinning in the api dependencies.
I understand that pinning is required, but having the pinning too strict can introduce problems as well:
Some package versions aren't available right away, and maintainers don't necessarily have time to upgrade there dependencies right away. This can introduce breakage for example in the docker file, when we have a cryptography==38.0.3, but the project requires ==38.0.4
I want to relax the pinning to accept '~' version (only patches, not major, no minor). I hope this middle ground will reduce friction and allow to cleanup some parts of the code.
Note that some dependencies still can be pinned, but I would prefer not the pin by default.