feat(sync): let devices share confirmed deletions through a syncDeletions collection
OpenTubeX asks before applying deletions that would empty a synced list, because it can't tell another device's deletion from a server that lost the data. When you unsubscribe from 3 or more channels on one device, sync pauses on your other devices until someone confirms there. OpenTubeX#3342 lets a device share the deletions its user confirmed in an encrypted syncDeletions collection, so the other devices apply them without asking. The app only does this when /health reports sync_deletions: 1.
The server now accepts the syncDeletions collection with a 16 MiB limit and reports sync_deletions: 1. The README lists the collection and the capability. Clients share this collection across profiles, so it has no per-profile scope.
Proof: the existing limit and /health tests now cover the collection and the capability. cargo test (107 tests), cargo fmt --check and cargo clippy --all-targets pass. I ran this branch locally and pointed the OpenTubeX network sync E2E tests at it: 12 passed and 1 skipped by design. That includes a new two-device test from OpenTubeX#3365, in which one device removes all 3 subscriptions and the other applies the removal and keeps automatic sync on. With sync_deletions hidden from /health, the same test fails with "Sync stopped because it would delete 3 of 3 previously synced subscriptions items".
Changes made by Claude Opus 5.5 in Claude Code (T3 Code).