First of the alpine pairs moved over. The two scripts become one with a section
per OS, the same shape as valkey in ProxmoxVED: setup_deb_based/setup_alpine in
the install script, update_deb_based/update_alpine in the ct script, dispatched
by run_os_setup and run_os_update.
The bootstrap now points at community-scripts/core rather than this repo's
misc/build.func, which is where those two dispatchers live. Nothing in misc/ is
touched.
_CS_DEFAULT_URL has to be set before sourcing: core resolves the scripts root
from the calling script's checkout, and when there is no checkout -- the usual
`bash -c "$(curl ...)"` -- it falls back to ProxmoxVED. A ProxmoxVE script would
then fetch its own -install.sh from the wrong repository. Setting only the
fallback keeps a local checkout and a fork resolving through their own git
remote, which is the point of that mechanism.
Verified: both files parse, the bootstrap resolves the scripts root to ProxmoxVE
and the engine to core, and the sections are the only functions defined.
ct/alpine-redis.sh and install/alpine-redis-install.sh are deliberately left in
place. They still run against misc/build.func, so bookmarked URLs keep working;
retiring them is a separate decision with user-facing consequences.