fix(web): ignore log catch-up replay frames

[metyatech]

Problem

Task, workflow run, and PR review log views load persisted history through REST and also keep a WebSocket open for live log frames. The WebSocket endpoints replay recent log rows with catchUp: true on connect/reconnect so clients do not miss events.

Those hooks were treating catch-up replay frames like normal live log frames after REST history had already loaded. On reconnect, the same recent log rows could therefore be appended again in the browser, making the log viewer show duplicate entries even though the persisted REST/DB history was not duplicated.

Session logs already avoid this by treating REST history as canonical and ignoring catchUp WebSocket frames. This PR applies the same policy to the other log hooks.

Summary

• Ignore WebSocket catchUp replay frames in task, workflow run, and PR review log hooks.
• Keep normal non-catch-up live log frames appending as before.
• Add regression coverage for catch-up replay frames.
• Add missing PR review log hook tests.

Verification

• pnpm --filter @optio/web test -- src/hooks/use-logs.test.ts src/hooks/use-workflow-run-logs.test.ts src/hooks/use-pr-review-logs.test.ts
• pnpm --filter @optio/web typecheck
• pnpm format:check
• pre-push pnpm turbo test completed successfully

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.