Adding more informative error messaging due to potential JWT and Clerk data discrepancy

[Andrewq11]

Changelogs

Due to the potential discrepancy between claims in JWTs issued from the Hub and the true data in Clerk, we want to provide users with a more informative error message in the event of forbidden errors (for upload) and not found errors (for downloads). More specifically, we would like to suggest to the user to retry logging in to get a fresh JWT with up-to-date claims from Clerk.

• Added error messaging suggesting a re-login in the case of 403 forbidden errors when a user tries to upload a dataset, benchmark or result.
• Added error messaging suggesting a re-login in the case of 404 not found errors when a user tries to retrieve a dataset or benchmark.
• Updated the doc strings for the above client methods with a helpful note regarding the potential discrepancy.

---

Checklist:

• Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
  • This came about from another PR: Allow an empty train partition to support test-set only (e.g. zero-shot) benchmarks #135
• Add tests to cover the fixed bug(s) or the newly introduced feature(s) (if appropriate).
• Update the API documentation if a new function is added, or an existing one is deleted.
• Write concise and explanatory changelogs above.
• If possible, assign one of the following labels to the PR: feature, fix, chore, documentation or test (or ask a maintainer to do it for you).

---

discussion related to that PR

[cwognum]

Thanks for the initiative, @Andrewq11 ! That is a nice quality of life improvement.

[cwognum]

Thanks again, @Andrewq11 ! Throwing custom exceptions in Python is not something I've really done before, so I'm learning with you here. I feel like the current approach is not very Pythonic and did some further suggestions that may help in that regard. Curious to hear what you think! Appreciate your patience.

I'm curious how other libs do this, e.g. numpy. No need to overthink it yet, but maybe there is some inspiration to be found there once we want more advanced functionality.

[cwognum]

@Andrewq11 With me being OOO, the time difference and the fast approaching deadline, I decide to make a PR into your branch to make my suggestions very explicit: #153.

I won't be available after 14:00 CET (08:00 EST), so you have my blessing to accept or reject these suggestions as you see fit and to merge this PR afterwards! 😉

[mercuryseries]

Thanks @Andrewq11! I added some minor comments/suggestions.