feat(quark): add Quark Drive adapter

[xiangzy1]

Summary

• Add browser-based adapter for Quark Cloud Drive (pan.quark.cn) with cookie strategy
• 7 commands: ls, mkdir, mv, rename, rm, save, share-tree
• Shared utilities (utils.ts) with API helpers, folder resolution, task polling, and file formatting
• Docs: adapter page + sidebar entry + index table row

Test plan

• opencli quark ls — list root directory
• opencli quark ls "path" --depth 3 — list with depth
• opencli quark mkdir "folder" --parent <fid> — create folder
• opencli quark mv "fid1,fid2" --to "path" — move files
• opencli quark rename <fid> --name "new.txt" — rename
• opencli quark rm "fid1,fid2" — delete files
• opencli quark save <url> --to "path" — save from share link
• opencli quark share-tree <url> — get share tree as JSON

[Astro-Han]

Useful adapter, and Quark is a sensible target for OpenCLI. The command set also feels about right for a first pass. I do not think this PR is ready yet, though. A few issues are correctness problems, and a few others miss the repo's current adapter standards.

The main code issues:

• clis/quark/ls.ts: the default --depth 1 behavior is off by one. As written, opencli quark ls walks into child folders instead of only listing the target folder. For an ls command, that default is surprising and can blow up output size on a normal drive.
• clis/quark/save.ts, clis/quark/mv.ts, clis/quark/utils.ts: save and mv report success before the async task is actually known to have succeeded. Right now a failed or timed out task can still come back as success: true or status: "ok" with completed: false, which hides real failures.
• clis/quark/save.ts, clis/quark/mv.ts: these commands accept both --to and --to-fid and silently prefer --to-fid. mkdir already rejects the equivalent ambiguous combination, and I think save / mv should do the same.
• clis/quark/utils.ts: the shared fetch helper assumes every response is JSON and immediately calls r.json(). If Quark returns an HTML login page, challenge page, or any other non-JSON response, this will throw a raw parse error instead of a normal CliError path.

The repo-standard gaps:

• No adapter tests. This repo already has adapter-level tests and browser auth-failure E2Es. For this PR I would at least expect unit coverage for the helper and validation logic, plus one graceful auth-failure case for quark.
• Missing README.md and README.zh-CN.md updates. The repo docs currently treat those as part of the deliverables for a new adapter.
• The new adapter doc is incomplete for a browser adapter. It should mention the Browser Bridge extension in prerequisites, not just "logged in to Quark Drive in Chrome".
• There is at least one incorrect example in the doc: mkdir --parent <fid> is wrong based on the implementation. --parent is a path, --parent-fid is the raw fid.
• The command table in the doc should show required positional args the same way other adapter docs do. Right now entries like opencli quark rename are too vague.
• A short notes section would help here, especially to explain that share-tree returns the stoken needed by save --fids.

From a contributor review perspective, I would fix the success-reporting and ls depth behavior first, then add the missing tests and README/doc follow-through before asking for merge.