Server type switches that just work

Highlights

• · Server type switches no longer fail mid-flight: switching a server's type (for example Purpur to Spigot, or Paper to Vanilla) used to show misleading dialog labels and fail to complete. The root cause was that two different parts of SpawnBox were separately managing the small telemetry helper that rides alongside your server (the SpawnBox Telemetry Datapack or Plugin, depending on server type - this is what powers Activity, Connected Players detail, base tracking, and combat insights). Their code paths could collide during same-family switches (Paper -> Purpur, for example) and flag filesystem work that didn't actually need to happen. Telemetry asset management is now consolidated into a single reconciliation pass that runs right before each server launch - one owner, no collisions. As a bonus side effect, the system self-heals if anything drifts out of alignment between launches.
• · Upgrades preserve your telemetry history: upgrading a server's type (for example Vanilla to Paper, to unlock plugin support) used to fail with a database is locked error if the server had already accumulated activity history. That migration path is now unblocked, and your telemetry history carries forward across the switch.
• · Kept-port imports land in the right configuration: importing a pre-existing server while keeping its original Minecraft port now correctly arranges the surrounding ports SpawnBox uses behind the scenes (for features like console access from the app and the Telemetry Plugin's data channel). Kept-port imports no longer collide with those slots or land on the wrong configuration.