Rollback XLA archival change, current automation does not calculate the shasum correctly

Reverts 6fee019

PiperOrigin-RevId: 785830039

Author: MichaelHudgins

third_party/xla/revision.bzl

@@ -17,7 +17,7 @@
 # To update XLA to a new revision,
 # a) update XLA_COMMIT to the new git commit hash
 # b) get the sha256 hash of the commit by running:
-#    curl -L https://api.github.com/repos/openxla/xla/tarball/{git_hash} | sha256sum
+#    curl -L https://github.com/openxla/xla/archive/<git hash>.tar.gz | sha256sum
 #    and update XLA_SHA256 with the result.
 
 # buildifier: disable=module-docstring

third_party/xla/workspace.bzl

@@ -20,12 +20,8 @@ def repo():
     tf_http_archive(
         name = "xla",
         sha256 = XLA_SHA256,
-        type = "tar.gz",
-        strip_prefix = "openxla-xla-{commit}".format(commit = XLA_COMMIT[:7]),
-        # We use an automated tool to update the revision.bzl file. GitHub prohibits the crawling of
-        # web links (`/archive/`) links so we use the GitHub API endpoint to get the tarball
-        # instead.
-        urls = tf_mirror_urls("https://api.github.com/repos/openxla/xla/tarball/{commit}".format(commit = XLA_COMMIT)),
+        strip_prefix = "xla-{commit}".format(commit = XLA_COMMIT),
+        urls = tf_mirror_urls("https://github.com/openxla/xla/archive/{commit}.tar.gz".format(commit = XLA_COMMIT)),
     )
 
     # For development, one often wants to make changes to the TF repository as well