Fix CinderX docs CI: point yarn.lock at the public package registry

Summary:
The `Documentation` GitHub Actions workflow was failing at the `Install dependencies` step (`yarn install --frozen-lockfile`) within ~14s, before the Docusaurus build ever ran. Every one of the 1278 `resolved` URLs in `cinderx/website/yarn.lock` pointed at the wrong registry, so yarn could not fetch any tarballs.

This rewrites all `resolved` URLs to `registry.yarnpkg.com`. The tarball paths and `#<sha1>` / `integrity` hashes are byte-identical between the two — only the host differs — so the lockfile still pins the exact same package versions (mirrors the pattern already used by `pyrefly/website/yarn.lock`).

It also relaxes the install step from `yarn install --frozen-lockfile` to plain `yarn install` so a future internal lockfile regeneration that reintroduces an internal-registry URL re-resolves against the public registry instead of hard-failing the job.

Reviewed By: mpage

Differential Revision: D110208647

fbshipit-source-id: a61ccb83475d833efae1d66a23ce4e54fe7f5eed

Author: javabster

.github/workflows/docs.yml

@@ -44,7 +44,7 @@ jobs:
           cache-dependency-path: cinderx/website/yarn.lock
 
       - name: Install dependencies
-        run: yarn install --frozen-lockfile
+        run: yarn install
 
       - name: Build (fails on broken links)
         run: yarn build