bisque-voice installers now download from GitHub Releases

bisque-voice installers would download from GitHub Releases instead of Google Cloud. Pull request five moves the binaries, the checksums and latest.json into the repository's own release, and the install scripts follow them there.

Until now a tagged release was published in two places. The full set went to a Google Cloud bucket behind download.bisque.today, including latest.json and both install scripts, and the workflow needed its own Google Cloud login to do it. The GitHub Release only carried the archives and the checksum list.

After this change the GitHub Release is the only home for the binaries. It carries every archive with its checksum file, the combined checksum list, and now latest.json too. Installers ask GitHub for the newest release through a fixed latest path, so there is no bucket to keep in sync.

In release.yml the upload job loses everything Google. The authentication step, the gcloud setup, the id-token permission, the check that refused to overwrite a published version, and the copy commands all go. The file shrinks by about forty lines and gains under twenty.

The reason to attach latest.json is in this comment. The installers resolve the newest release's latest.json, so it must never name an archive that isn't attached yet. That is why one call creates the release with every file. The call now also attaches the per-archive checksum files and latest.json.

# One call with every file, so the release appears
# complete or not at all: latest.json must never
# name an archive that isn't attached yet.
gh release create "$GITHUB_REF_NAME" --verify-tag \
  --title "bisque-voice $VERSION" \
  --notes-file notes.md \
  artifacts/*.tar.gz artifacts/*.tar.gz.sha256 \
  artifacts/SHASUMS256.txt latest.json

In install.sh, the default now points at the repository's releases. GitHub serves the newest release under releases slash latest slash download, so latest.json is fetched from there. The override variable still wins. When someone sets it, the base and latest.json both come from that directory, which keeps the offline file URL testing path working.

if [ -n "${BISQUE_VOICE_BASE_URL:-}" ]; then
  BASE="$BISQUE_VOICE_BASE_URL"
  LATEST="$BASE/latest.json"
else
  BASE="$RELEASES/download"
  LATEST="$RELEASES/latest/download/latest.json"
fi

install.ps1 gets the same logic, with a default base of the GitHub Releases download path. The scripts themselves stay at download.bisque.today, and the workflow comment says why. The Windows hint in install.sh and the Linux hint in install.ps1 keep pointing at that address.

There is one limit. Versions before 0.1.38 were built elsewhere and are not attached to any GitHub Release. To install one, INSTALL.md tells you to set the base URL variable back to the old address.

BISQUE_VOICE_BASE_URL=\
https://download.bisque.today/bisque-voice \
  sh install.sh

The pull request body says only update bisque-voice, so there are no test results to point at. The diff assumes the old install addresses already redirect to main, and nothing in these four files sets that up. With that in place, installers download from GitHub Releases and a release lives in one place.