Pin click to z-streams

[mdellweg]

It turns out the click library introduces breaking changes with y-releases.

(cherry picked from commit 6d643dd) (cherry picked from commit 1eafe5c) (cherry picked from commit 3c1cba5)

[patchback]

Backport to 0.29: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply f68b7ef on top of patchback/backports/0.29/f68b7ef0202e8f6bef217f7755c084505df26948/pr-1193

Backporting merged PR #1193 into 0.30

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/pulp/pulp-cli.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/0.29/f68b7ef0202e8f6bef217f7755c084505df26948/pr-1193 upstream/0.29

4. Now, cherry-pick PR Pin click to z-streams #1193 contents into that branch:

   $ git cherry-pick -x f68b7ef0202e8f6bef217f7755c084505df26948

   If it'll yell at you with something like fatal: Commit f68b7ef0202e8f6bef217f7755c084505df26948 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x f68b7ef0202e8f6bef217f7755c084505df26948

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Pin click to z-streams #1193 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/0.29/f68b7ef0202e8f6bef217f7755c084505df26948/pr-1193

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.