update: remove the obsolete standard/ui variant chooser; add ui-* alias assets so 0.9.x updaters stop 404ing

[DeusData]

From discussion #1526 (@iandol): upgrading 0.9.0 → 0.10.0 via codebase-memory-mcp update offers the standard/ui variant choice; picking "ui" downloads codebase-memory-mcp-ui-linux-amd64-portable.tar.gz → 404, because v0.10.0 consolidated to a single archive per platform with the UI always embedded.

Two defects:

1. The chooser still ships in current binaries (select_update_variant, src/cli/cli.c:11355): it presents a choice that no longer exists — "ui" can only 404, and "standard" quietly IS the full UI build. Remove the chooser; update downloads the one real archive. Also purge the CBM_VARIANT=ui remnants from pkg/npm/install.js / pypi equivalents (the variant is gone).
2. Released 0.9.x binaries can't be fixed retroactively, but their updaters hit releases/latest/download/codebase-memory-mcp-ui-<platform>.tar.gz — so the release workflow should attach ui-*-named alias assets (same bytes, legacy names) for the transition window. That makes every old updater work again with zero user action.

Slated for v0.10.2. The install.sh staging failure from the same discussion is tracked separately in #1535 (second environment report — not WSL2-specific).

[DeusData]

Fixed in v0.10.2, released just now: https://github.com/DeusData/codebase-memory-mcp/releases/tag/v0.10.2 (GitHub archives, npm, and PyPI are all serving it).

Please give it a try when you get a chance — if it behaves in your setup, feel free to close this out; if anything still looks off, say so and we'll pick it straight back up. Thank you again for the report, it made this fix fast and precise.