Publish Agave docs

[willhickey]

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

[yihau]

🪖

[mergify]

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

[mergify]

Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule.