Allow to access the admin routes programmatically
Currently, the admin endpoints are protected with Okta SSO:

https://datasets-server.huggingface.co/admin/pending-jobs
https://datasets-server.huggingface.co/admin/cache-reports/splits
https://datasets-server.huggingface.co/admin/cache-reports/first-rows

But we cannot access these URLs programmatically, see 

https://observablehq.com/@huggingface/datasets-server-jobs-queue
https://observablehq.com/@huggingface/internal-datasets-server-cache-contents

Ideally we would be able to pass an API token (from https://huggingface.co/settings/tokens) and get access to the contents if member of the huggingface organization.

Maybe the idea is to:
- add an authentication call to `https://huggingface.co/api/whoami-v2` with the token (if any has been provided through the `authorization` header)
- if the response is 200 and the user is a member of the https://huggingface.co/huggingface, return the response, else an error
- then: remove the Okta SSO protection (set up on the kubernetes ingress)

wdyt @XciD @julien-c @Pierrci @coyotte508 @SBrandeis?
Allow to access the admin routes programmatically: Currently, the admin endpoints are protected with Okta SSO:

https://datasets-server.huggingface.co/admin/pending-jobs
https://datasets-server.huggingface.co/admin/cache-reports/splits
https://datasets-server.huggingface.co/admin/cache-reports/first-rows

But we cannot access these URLs programmatically, see 

https://observablehq.com/@huggingface/datasets-server-jobs-queue
https://observablehq.com/@huggingface/internal-datasets-server-cache-contents

Ideally we would be able to pass an API token (from https://huggingface.co/settings/tokens) and get access to the contents if member of the huggingface organization.

Maybe the idea is to:
- add an authentication call to `https://huggingface.co/api/whoami-v2` with the token (if any has been provided through the `authorization` header)
- if the response is 200 and the user is a member of the https://huggingface.co/huggingface, return the response, else an error
- then: remove the Okta SSO protection (set up on the kubernetes ingress)

wdyt @XciD @julien-c @Pierrci @coyotte508 @SBrandeis?