Remove testing of twine's --skip-existing due to twine feature removal

[gerrod3]

No description provided.

[ggainey]

Specifically respond to twine's recent changelog "Remove hacks that support --skip-existing for indexes other than PyPI and TestPyPI"

[patchback]

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

❌ Failed to cleanly apply 2b34643 on top of patchback/backports/3.11/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957

Backporting merged PR #957 into main

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_python.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/3.11/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957 upstream/3.11

4. Now, cherry-pick PR Remove testing of twine's --skip-existing due to twine feature removal #957 contents into that branch:

   $ git cherry-pick -x 2b34643299835462a4add6b3b76d2d8309bf91d9

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

   $ git cherry-pick -m1 -x 2b34643299835462a4add6b3b76d2d8309bf91d9

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Remove testing of twine's --skip-existing due to twine feature removal #957 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957

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.

[patchback]

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

❌ Failed to cleanly apply 2b34643 on top of patchback/backports/3.12/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957

Backporting merged PR #957 into main

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_python.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/3.12/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957 upstream/3.12

4. Now, cherry-pick PR Remove testing of twine's --skip-existing due to twine feature removal #957 contents into that branch:

   $ git cherry-pick -x 2b34643299835462a4add6b3b76d2d8309bf91d9

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

   $ git cherry-pick -m1 -x 2b34643299835462a4add6b3b76d2d8309bf91d9

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Remove testing of twine's --skip-existing due to twine feature removal #957 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.12/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957

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.

[patchback]

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

❌ Failed to cleanly apply 2b34643 on top of patchback/backports/3.13/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957

Backporting merged PR #957 into main

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_python.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/3.13/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957 upstream/3.13

4. Now, cherry-pick PR Remove testing of twine's --skip-existing due to twine feature removal #957 contents into that branch:

   $ git cherry-pick -x 2b34643299835462a4add6b3b76d2d8309bf91d9

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

   $ git cherry-pick -m1 -x 2b34643299835462a4add6b3b76d2d8309bf91d9

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Remove testing of twine's --skip-existing due to twine feature removal #957 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.13/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957

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.

[patchback]

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

❌ Failed to cleanly apply 2b34643 on top of patchback/backports/3.10/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957

Backporting merged PR #957 into main

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_python.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/3.10/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957 upstream/3.10

4. Now, cherry-pick PR Remove testing of twine's --skip-existing due to twine feature removal #957 contents into that branch:

   $ git cherry-pick -x 2b34643299835462a4add6b3b76d2d8309bf91d9

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

   $ git cherry-pick -m1 -x 2b34643299835462a4add6b3b76d2d8309bf91d9

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Remove testing of twine's --skip-existing due to twine feature removal #957 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957

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.

[patchback]

Backport to 3.19: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.19/2b34643299835462a4add6b3b76d2d8309bf91d9/pr-957

Backported as #958

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