Follow /auth-check 307 redirections

See https://github.com/huggingface/datasets-server/issues/1655#issuecomment-1923688766: as the dataset has been renamed, an internal call to /auth-check returns a 307 redirection, but we don't follow it.

More generally, we should handle redirections in all the code (I think it's always handled by huggingface_hub, so it should be only in our custom requests)

Start by locating the custom requests that call /auth-check and other internal endpoints; the issue indicates these may not use huggingface_hub's redirect handling. Verify the 307 response path, then confirm that custom requests follow redirects consistently and that the renamed dataset flow succeeds.

Written by the indexing model from the issue text.