feat: Add Uptime Kuma auto-update

Docker compose update via SSH to abraham.jeena.net. Review examples
include real v2.x patches as auto and the v1→v2 migration as manual,
plus a synthetic v2→v3 breaking change example.

Also fix test_classifier.py version derivation for x.0.0 releases
where patch decrement would produce the same version, causing the
model to see a nonsensical "upgrading from 2.0.0 to 2.0.0" prompt.

services/uptime-kuma/review-examples/manual-2.txt

@@ -0,0 +1,14 @@
+action: manual
+reason: Major version 3.0 changes the Docker volume mount path from /app/data to /data and requires a new environment variable for the database connection. Admin must update docker-compose.yaml before upgrading.
+---
+> [!WARNING]
+> Major version update with breaking changes. Please read the migration guide before upgrading.
+
+Migration Guide: https://github.com/louislam/uptime-kuma/wiki/Migration-From-v2-To-v3
+
+### Breaking changes
+
+- The data directory inside the container has changed from `/app/data` to `/data`. Update your docker-compose volume mounts accordingly.
+- A new required environment variable `DATABASE_URL` must be set for the database connection. The old embedded SQLite configuration is no longer the default.
+- The notification template engine has been replaced. Custom notification templates must be rewritten using the new syntax.
+- The API authentication has changed from basic auth to token-based auth. API integrations must be updated.