fix: support per-server max/from/to in cycle transfer stats (#64)

* Initial plan

* fix: support per-server max/from/to values in cycle transfer stats

When the Nezha backend has multiple transfer rules within one alert rule,
the API may return per-server max values (as a map) instead of a single
max value. Update the TypeScript interface and CycleTransferStats component
to handle both formats:
- Single value (number/string): used for all servers (current behavior)
- Per-server map ({[serverId]: value}): uses the correct value per server

Fixes #63

Agent-Logs-Url: https://github.com/hamster1963/nezha-dash-v2/sessions/88f98dad-c2eb-4728-ac98-e02a95d5144d

Co-authored-by: hamster1963 <71394853+hamster1963@users.noreply.github.com>

* fix: update schema version in biome.json and improve null checks in components

* chore: auto-fix linting and formatting issues

* fix: guard null/zero in CycleTransferStats per-server map lookups

Agent-Logs-Url: https://github.com/hamster1963/nezha-dash-v2/sessions/2fb2306b-8011-487d-b284-9768778db8c3

Co-authored-by: hamster1963 <71394853+hamster1963@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: hamster1963 <71394853+hamster1963@users.noreply.github.com>
Co-authored-by: hamster1963 <1410514192@qq.com>

src/components/ui/command.tsx

@@ -149,11 +149,11 @@ CommandShortcut.displayName = "CommandShortcut";
 export {
 	Command,
 	CommandDialog,
-	CommandInput,
-	CommandList,
 	CommandEmpty,
 	CommandGroup,
+	CommandInput,
 	CommandItem,
-	CommandShortcut,
+	CommandList,
 	CommandSeparator,
+	CommandShortcut,
 };