triage anaconda upload failure

[ndgrigorian]

• Have you provided a meaningful PR description?
• Have you added a test, reproducer or referred to an issue with a reproducer?
• Have you tested your changes locally for CPU and GPU devices?
• Have you made sure that new changes do not introduce compiler warnings?
• Have you checked performance impact of proposed changes?
• Have you added documentation for your changes, if necessary?
• Have you added your changes to the changelog?
• If this PR is a work in progress, are you opening the PR as a draft?

[github-actions]

Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. 🤞

[github-actions]

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_125 ran successfully.
Passed: 1115
Failed: 6
Skipped: 119

[coveralls]

coverage: 85.269%. remained the same
when pulling 6905f01 on triage-conda-upload-failure
into 33069cb on master.

[github-actions]

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_126 ran successfully.
Passed: 1115
Failed: 6
Skipped: 119

[github-actions]

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_127 ran successfully.
Passed: 1115
Failed: 6
Skipped: 119

[github-actions]

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_128 ran successfully.
Passed: 1114
Failed: 7
Skipped: 119

[github-actions]

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_129 ran successfully.
Passed: 1114
Failed: 7
Skipped: 119

[github-actions]

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_128 ran successfully.
Passed: 1115
Failed: 6
Skipped: 119

[github-actions]

Array API standard conformance tests for dpctl=0.21.0dev0=py310h93fe807_128 ran successfully.
Passed: 1115
Failed: 6
Skipped: 119

[ndgrigorian]

the issue seems to have been connected to an issue between anaconda-client and anaconda-auth, but it remains unknown why this only surfaced when the token was regenerated (caching somewhere?)

either way, this is a successful POC for a fix in a separate PR