Deprecate usage of latest branch

[paoloredis]

Merging to main will publish directly to redis.io/docs/latest . the latest branch will be removed altogether

---

Note

Medium Risk
Changes which Git branch triggers live docs deploys and GCS paths; a misconfigured set-paths step could publish staging content to production or skip the 404 deploy until caught in CI.

Overview
Production publishing moves from the latest Git branch to main. Merges to main now set hugo_root_path/bucket_path to the live /docs/latest targets; the old mapping that sent main to docs/staging/dev and reserved production for a latest branch is removed.

Deploy logic keys off bucket_path instead of branch name. Kubernetes, RS, RDI, and RedisVL GCS deploy steps and the custom 404 job now treat production uploads when bucket_path == 'latest' (so main qualifies), not when github.ref_name == 'latest'.

Contributor docs in README.md describe auto-publish on merge to main, per-PR staging previews, and drop the manual main → latest promotion workflow.

^{Reviewed by Cursor Bugbot for commit 57251d5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

DOC-6867

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[mich-elle-luna]

thank you!