Fix pip deployment and extend deploy rule doc strings with usage

What is the goal of this PR?

The deploy_pip rule was modified by #368 to allow deploying wheels and targz packages to repositories provided by a pypirc file. However, this broke this repository's consistent design: every deploy_* rule provides all possible repositories to upload to (eg. using snapshot or release), then selects which one to deploy to at run time using arguments.

This PR revert some changes to the deploy_pip rule to make it conform to this consistent design. We also fix some bugs during the upload process.

Finally, we extend the doc strings for each of the deploy rules to indicate how to select the repository to deploy to.

`deploy_pip` changes

The deploy_pip rule is changed to take multiple different destination repositories to upload to. These are provided, as before, using the existing snapshot or release attributes. The additional attribute of pypirc_repository (renamed from pypi_profile) is made available in the same way, rather than with an exclusive-or logic.

Now we declare deploy_pip targets like this:

deploy_pip(
  name = "some-deploy-pip",
  snapshot = "https://... snapshot ...",
  release = "https:// ... release ...",
  pypirc_repository = "some-repository-name"
)

The pypirc_repository attribute refers the name of a repository declared in a pyripc file. This configuration file is an external file normally exists in a standard location such as $HOME/.pypirc.

After this change, deployment looks like this:

bazel run //:some-deploy-pip -- [pypirc|snapshot|release]

All deployment rules in this repository should continue to support declaring multiple target repositories in this manner, for the time being.

What are the changes implemented in this PR?

Add doc strings to show how to use deployment rules for either snapshot or release
Refactor deploy_pip to be consistent with the existing style, in which all potential deployment repositories are declared by attribute and the relevant one is selected as an argument to bazel run //... -- [arg]
Fix the upload of the .tar.gz and .whl packages to the target repository, which was failing because of non-existent paths
Downgrade setuptools to version 65.0.0, which still allows non-semantic versioned packages to distributed and is a requirement for Vaticle for now

PR Review Checklist

Do not edit the content of this comment. The PR reviewer should simply update this comment by ticking each review item below, as they get completed.

Trivial Change

[ ] This change is trivial and does not require a code or architecture review.

Code

[ ] Packages, classes, and methods have a single domain of responsibility.
[ ] Packages, classes, and methods are grouped into cohesive and consistent domain model.
[ ] The code is canonical and the minimum required to achieve the goal.
[ ] Modules, libraries, and APIs are easy to use, robust (foolproof and not errorprone), and tested.
[ ] Logic and naming has clear narrative that communicates the accurate intent and responsibility of each module (e.g. method, class, etc.).
[ ] The code is algorithmically efficient and scalable for the whole application.

Architecture

[ ] Any required refactoring is completed, and the architecture does not introduce technical debt incidentally.
[ ] Any required build and release automations are updated and/or implemented.
[ ] Any new components follows a consistent style with respect to the pre-existing codebase.
[ ] The architecture intuitively reflects the application domain, and is easy to understand.
[ ] The architecture has a well-defined hierarchy of encapsulated components.
[ ] The architecture is extensible and scalable.

vaticle / bazel-distribution