chore(firecracker): name the artifact package bot-bottle-firecracker-infra

Rename the Gitea generic package from bot-bottle-infra to
bot-bottle-firecracker-infra so it's self-evident in the package list which
backend it serves (and leaves room for other artifacts, e.g. a shipped
kernel). The version slot stays the content hash — "firecracker" belongs in
the package name, not the version. Docker image / VM names are unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UoEZHDjv84ChoZbozQERhJ

docs/prds/0069-firecracker-native-docker-free.md

@@ -112,12 +112,12 @@ bottle-agnostic**: the per-boot bits (authorized_keys, guest IP) arrive on the
 published ext4 boots on any launch host.
 
 - **Artifact.** `rootfs.ext4` + a `rootfs.ext4.sha256`, published as a Gitea
-  **generic package** (`bot-bottle-infra/<tag>`) — generic packages take
+  **generic package** (`bot-bottle-firecracker-infra/<tag>`) — generic packages take
   arbitrary large binaries (no attachment size cap / file-type allowlist that
   release attachments impose). The matching `vmlinux` kernel can ship the same
   way, so the whole VM is fetchable.
 - **Pull.** The launch host `GET`s
-  `…/api/packages/<owner>/generic/bot-bottle-infra/<tag>/rootfs.ext4` (+
+  `…/api/packages/<owner>/generic/bot-bottle-firecracker-infra/<tag>/rootfs.ext4` (+
   `.sha256`) for its pinned tag, verifies the checksum, caches it under the
   tag, and attaches it as the infra VM's root disk. Host prerequisite is an
   HTTP client — nothing else. Public packages need no auth to pull; a token