refactor(tools)!: consolidate 15 individual tools into single unified unraid tool

BREAKING CHANGE: Replaces 15 separate MCP tools (unraid_info, unraid_array,
unraid_storage, unraid_docker, unraid_vm, unraid_notifications, unraid_rclone,
unraid_users, unraid_keys, unraid_health, unraid_settings, unraid_customization,
unraid_plugins, unraid_oidc, unraid_live) with a single `unraid` tool using
action (domain) + subaction (operation) routing.

New interface: unraid(action="system", subaction="overview") replaces
unraid_info(action="overview"). All 15 domains and ~108 subactions preserved.

- Add unraid_mcp/tools/unraid.py (1891 lines, all domains consolidated)
- Remove 15 individual tool files
- Update tools/__init__.py to register single unified tool
- Update server.py for new tool registration pattern
- Update subscriptions/manager.py and resources.py for new tool names
- Update all 25 test files + integration/contract/safety/schema/property tests
- Update mcporter smoke-test script for new tool interface
- Bump version 0.6.0 → 1.0.0

Co-authored-by: Claude <noreply@anthropic.com>

tests/integration/test_subscriptions.py

@@ -125,6 +125,24 @@ class TestSubscriptionManagerInit:
         cfg = mgr.subscription_configs["logFileSubscription"]
         assert cfg.get("auto_start") is False
 
+    def test_subscription_configs_contain_all_snapshot_actions(self) -> None:
+        from unraid_mcp.subscriptions.queries import SNAPSHOT_ACTIONS
+
+        mgr = SubscriptionManager()
+        for action in SNAPSHOT_ACTIONS:
+            assert action in mgr.subscription_configs, (
+                f"'{action}' missing from subscription_configs"
+            )
+
+    def test_snapshot_actions_all_auto_start(self) -> None:
+        from unraid_mcp.subscriptions.queries import SNAPSHOT_ACTIONS
+
+        mgr = SubscriptionManager()
+        for action in SNAPSHOT_ACTIONS:
+            assert mgr.subscription_configs[action].get("auto_start") is True, (
+                f"'{action}' missing auto_start=True"
+            )
+
 
 # ---------------------------------------------------------------------------
 # Connection Lifecycle