#20695: Add openclaw-workspace-sync to community plugins

## Summary - Adds **Workspace Cloud Sync** (`openclaw-workspace-sync`) to the community plugins listing in `docs/plugins/community.md` This is a standalone community plugin for bidirectional workspace sync via rclone, supporting Dropbox, Google Drive, OneDrive, S3, and 70+ cloud providers. Zero LLM cost. - **npm:** [openclaw-workspace-sync](https://www.npmjs.com/package/openclaw-workspace-sync) - **Repo:** [ashbrener/openclaw-workspace-sync](https://github.com/ashbrener/openclaw-workspace-sync) - **Install:** `openclaw plugins install openclaw-workspace-sync` Built as a community plugin per @steipete's feedback on #19052. Tracked in #18106. Addresses community requests: #17913, #17418, #13616, #7598, #8255, #2597 Replaces #20440 (closed due to merge conflict from stale fork base). ## Test plan - [ ] Verify `docs/plugins/community.md` renders correctly - [ ] Verify the install command works: `openclaw plugins install openclaw-workspace-sync` - [ ] Confirm `plugins/community` is already in `docs/docs.json` navigation (line ~1005) <!-- greptile_comment --> <h3>Greptile Summary</h3> Adds `openclaw-workspace-sync` plugin to the community plugins documentation page. The entry follows the documented format exactly with plugin name, description, npm package, repository link, and install command. The change is straightforward: it adds a new plugin listing under the "Listed plugins" section without modifying any existing content. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk - The change is a simple documentation addition that follows the established format perfectly. It only adds a new plugin listing without modifying any code or existing documentation structure. The formatting matches the template exactly (proper indentation, required fields, correct syntax). - No files require special attention _{Last reviewed commit: cd62fae} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->