v2.0: Publish Agave docs (backport of #2887)

[mergify]

Problem

Agave docs don't publish anywhere

Summary of Changes

Turn the docs publishing pipeline back on.

This is tricky to test properly without merging first. I've tested it from my dev server by running this:

#!/usr/bin/env bash

export VERCEL_TOKEN="***"
export VERCEL_SCOPE="***"
echo "Starting npm install"
npm install
echo "Starting ./build.sh"
./build.sh

Which produces builds here:
https://vercel.com/anza-tech/docs/deployments

Looking through .github/workflows/docs.yml, docs/build.sh, and docs/publish-docs.sh I think the old logic logic should still work. I'd like to merge this and test it in production. Once it's publishing correctly I can setup a DNS record for: edge.docs.anza.xyz

And then backport this PR (plus any follow ups) before setting up DNS records for:
beta.docs.anza.xyz
docs.anza.xyz

---

This is an automatic backport of pull request #2887 done by Mergify.

[bw-solana]

I'm assuming the publishing pipeline has been confirmed working now?

[willhickey]

This is working correctly on master:
PR #2094 triggered a build here (404 if you're not authorized):
https://vercel.com/anza-tech/edge-docs-anza-xyz/BuARmeZknXuE64UbX2tnZH9SCYbR

Which publishes to https://edge.docs.anza.xyz/ Notice that the tonic link is now correct here as fixed by PR #2094

Once this PR is merged changes to v2.0 docs will be published to beta.docs.anza.xyz and docs.anza.xyz. I will open another PR to v1.18 for publishing to stable.docs.anza.xyz.

[yihau]

🪖