packaging commonhealth-cloud-storage-client on conda-forge

[minrk]

@fperez asked to package the common health cloud Python client to be on conda-forge

Current impediments:

• strict version pinning in the package. See Python packaging recommendations, but it's usually not a good idea to pin exact dependencies in a package, as that causes conflicts with other packages. Pinning is usually a good idea when building docker images, etc., but that's best done in an external requirements.txt managed through something like pip-compile, dependabot, etc.
• tink is a dependency that is also not yet on conda-forge (I can manage, it'll just take a bit because it uses bazel, a build system I'm not familiar with)

cc @surfdoc for the package pinning

This is not pressing, and can be done comfortably after pre-MVP. It does not block anything. Fixing the pinning would help a bit for the pre-MVP, but can be worked around without too much trouble for now.

[minrk]

version pinning is addressed in 1.0.5, tink will require more time

[minrk]

The new MVP architecture removes cryptography responsibilities from the partner, which I assume will remove tink from the dependency list. That should make packaging the next version of the client on conda-forge easier.