https://bazel.build/bazel-release.pub.gpg 404

### Description of the bug:

I can't get gpg keys from https://bazel.build/bazel-release.pub.gpg use curl. And I also can't open this link on my Chrome.
$ curl -fsSL https://bazel.build/bazel-release.pub.gpg | apt-key add -
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
curl: (28) Failed to connect to bazel.build port 443 after 134877 ms: Connection timed out
gpg: no valid OpenPGP data found.

### Which category does this issue belong to?

_No response_

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

_No response_

### Which operating system are you running Bazel on?

_No response_

### What is the output of `bazel info release`?

_No response_

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

_No response_

### If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Start by reproducing the curl request for https://bazel.build/bazel-release.pub.gpg and compare the reported 404 title with the connection-timeout output. The issue names no Bazel file, test, or release entry point, so first identify which repository or release configuration serves this key; done means the documented key retrieval path returns valid OpenPGP data.

Written by the indexing model from the issue text.