feat: WMT client versioning, release management and force-update playbook

- api/wmt.py: add GET /api/wmt/client/version and GET /api/wmt/client/download endpoints; rewrite submit_update_request with dedup logic
- web/wmt.py: add releases, releases_upload, releases_delete, releases_build routes; build-from-folder excludes hidden/data/venv/pyc files
- web/main.py: admin per-device delete route; clear-device-logs route; pass devices list to admin template
- templates/wmt/releases.html: new release management page (current release info, upload form, build-from-folder card)
- templates/admin.html: replace nuclear clear-devices with clear-logs + per-device delete table
- templates/base.html: add Client Releases nav link in WMT sidebar section
- templates/ansible/execute.html: add Update WMT Code playbook card
- ansible/playbooks/update_wmt_code.yml: rsync WMT_project to clients excluding data/; backs up app.py; restarts wmt service
- ansible_service.py: register update_wmt_code description
- .gitignore: whitelist update_wmt_code.yml

app/services/ansible_service.py

@@ -737,6 +737,7 @@ class AnsibleService:
             'system_health': 'Check system health and monitoring status',
             'maintenance_mode': 'Put devices in maintenance mode',
             'distribute_ssh_keys': 'Push server public key to all devices using password auth',
+            'update_wmt_code': 'Push WMT_project code to clients from controller (preserves data/)',
         }
         return descriptions.get(playbook_name, f'Execute {playbook_name} playbook')