patches: add v1.11.0 series and retire v1.10.0

Upstream released v1.11.0 (e42ae7a, 2026-11-06): 42 commits, mostly
fixes, plus two WebUI features that add ~415 lines to explorer.html
(on-demand bucket size calculation, restore archived objects).

The series needed no content changes — the regenerated patches differ
from the v1.10.0 ones only in their `index <blob>..<blob>` lines, since
the de-brand edits sit above the regions upstream touched.  Regenerating
them is still worthwhile: the v1.10.0 patches' pre-image blobs do not
exist in a v1.11.0 clone, so `git am --3way` could not use its 3-way
fallback and was silently applying them directly.

Verified before committing:
  - round-trips from a clean clone to tree 8d509fe
  - residual branding identical to the patched v1.10.0 tree (23
    occurrences, same per-file spread, no regressions)
  - all 5 light-mode Tailwind classes in the new explorer markup are
    overridden in theme.css
  - series touches only webui/; file count 1049 -> 1051
  - goreleaser builds all 8 targets plus deb/rpm
  - matrix accepts v1.11.0, refuses v1.10.0, PATCH_DIR still rebuilds
    the archived series

v1.10.0 moves to patches/archive/ as *superseded*, not vulnerable: it is
the release carrying upstream's CVE-2026-111943 notice, and that fix
comes from the Go toolchain (>= 1.26.10 / 1.27.3) rather than from the
tag.  The archive README and the top-level README now say so, instead of
implying every archived series predates a security fix.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/multi-version-pipeline.md

@@ -45,8 +45,8 @@ Each build is four steps, run for a single upstream tag:
 
 ```yaml
 versitygw:
-  - tag: v1.10.0
-    patches: v1.10.0
+  - tag: v1.11.0
+    patches: v1.11.0
 ```
 
 - `tag` — upstream git tag.
@@ -156,6 +156,6 @@ PATCH_DIR=patches/archive/v1.8.0 VGW_TAG=v1.8.0 bash ci/apply-patches.sh
 ## Release tagging
 
 Releases are created in this repo with the **upstream** tag name
-(`v1.10.0`). If you need to ship a rebuild of the same upstream version
+(`v1.11.0`). If you need to ship a rebuild of the same upstream version
 (e.g. a patch fix), set `RELEASE_TAG` in `ci/publish-release.sh`'s
-environment to something like `v1.10.0-acg2` to avoid clobbering.
+environment to something like `v1.11.0-acg2` to avoid clobbering.