refactor!: fix P9 interface-shape lies in workflow and analytics (#350)

[foxzool]

Summary

Closes the remaining #350 (P9 interface-shape lies) work after platform/user were fixed earlier.

• workflow: approve_task / reject_task / resubmit_task no longer discard the real response and return a forever-true ApprovalTaskActionResult { success: true }. They now return SDKResult<()> (Feishu approval v4 action data is empty). ApprovalTaskActionResult removed.
• analytics: Delete search/v2/query.rs and user.rs runtime stubs that always returned Err with unused setters (no verified Feishu endpoints; same honesty direction as [refactor] analytics: 给 Search/SearchV2/search() 标 #[deprecated]（为下个 breaking 窗口铺路） #308 facade removal). AnalyticsService::new: SDKResult<Self> → Self; client facade drops ?.
• platform / user (already on main): PlatformService::new (refactor(platform)!: 修 PlatformService::new 误导签名（#350 P9 platform 子项） #373), UserService::new (refactor(user): 砍 PersonalSettingsResource 中间层 + 修 UserService::new 误导签名（ADR 0001 阶段2） #360) — documented only, not re-done.

Migration

// workflow helpers
// before
let r = service.approve_task(action).await?;
if r.success { /* always true on Ok */ }

// after
service.approve_task(action).await?; // Ok = success

// analytics
// before
let s = AnalyticsService::new(config)?;
// after
let s = AnalyticsService::new(config);
// Prefer live search leaves: doc_wiki / schema / app / message / data_source

Test plan

• cargo test -p openlark-workflow --all-features (incl. new wiremock success + error helpers)
• cargo test -p openlark-analytics --all-features
• cargo clippy -p openlark-workflow -p openlark-analytics -p openlark-client --all-targets --all-features -- -Dwarnings
• cargo clippy -p openlark-workflow -p openlark-analytics --all-targets --no-default-features -- -Dwarnings
• cargo fmt --all -- --check
• CI green on this PR

Closes #350

---

Note

Medium Risk
Breaking public API changes in workflow helpers and analytics construction/search surface; behavior is more honest but callers must migrate off removed types and ? on AnalyticsService::new.

Overview
Breaking API honesty fixes (#350) for workflow and analytics, aligning with earlier platform/user Service::new corrections.

Workflow: approve_task, reject_task, and resubmit_task now return SDKResult<()> instead of always-true ApprovalTaskActionResult { success: true }. The helpers propagate real HTTP/leaf errors and drop the fake success field. Migration: use service.approve_task(...).await? instead of checking r.success.

Analytics: Removes search/v2/query and search/v2/user modules (always-Err stubs with dead setters; no verified Feishu endpoints). AnalyticsService::new changes from SDKResult<Self> to Self; openlark-client analytics init no longer uses ?. Callers should use live search leaves (doc_wiki, schema, app, message, data_source).

Docs, changelog, openspec, examples, and wiremock tests in openlark-workflow lock the new helper contract.

^{Reviewed by Cursor Bugbot for commit d26625c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_6ac7aa06-3b88-4762-9d68-9d6feae14771)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_bd43df38-6fd8-4b16-867f-7f310c6d606a)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_5f7105d4-8600-47d6-9b67-afb9e4a8ff79)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_26ae3080-b8e6-4874-8a80-99bb1f792f01)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_b163a5a9-02ec-4045-b1da-1e63c273e7fd)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_ce9624ec-3873-40e0-a7ee-4690da2ee987)