Yield the cost in usage data for Anthropic

[cte]

Description

Some providers aren't set up to yield costs in real-time. In some of these cases we sum the cost ourselves and yield a final usage with the total cost. For providers that don't do this there is a final fallback:

const updateApiReqMsg = (cancelReason?: ClineApiReqCancelReason, streamingFailedMessage?: string) => {
  this.clineMessages[lastApiReqIndex].text = JSON.stringify({
    ...JSON.parse(this.clineMessages[lastApiReqIndex].text || "{}"),
    tokensIn: inputTokens,
    tokensOut: outputTokens,
    cacheWrites: cacheWriteTokens,
    cacheReads: cacheReadTokens,
    cost:
      totalCost ??
      calculateApiCostAnthropic(
        this.api.getModel().info,
        inputTokens,
        outputTokens,
        cacheWriteTokens,
        cacheReadTokens,
      ),
    cancelReason,
    streamingFailedMessage,
  } satisfies ClineApiReqInfo)
}

This incorrectly assumes that the total cost calculation is the Anthropic variant, and it also happens after we emit the LLM Completion event that Roo Code Cloud uses.

The option that makes sense to me is to have our provider classes emit a usage with the total cost. Here's the fix for the Anthropic provider and I'm having Roo Code audit all of the others.

---

Important

Ensure Anthropic provider yields usage data with total cost by updating AnthropicHandler and Task classes.

• Behavior:
  • AnthropicHandler in anthropic.ts now accumulates token usage and yields a final usage event with totalCost using calculateApiCostAnthropic().
  • Task in Task.ts updates telemetry capture to calculate cost using calculateApiCostAnthropic() if totalCost is undefined.
• Tests:
  • Increase test timeout in ShadowCheckpointService.spec.ts from 10,000 to 20,000 milliseconds.

^{This description was created by for 53f048c. You can customize this summary. It will automatically update as commits are pushed.}

[cte]

This is flaking for the win32 GHA runner.

[cte]

Ideally we'd require all providers to emit a totalCost, but there's no enforcement mechanism for that right now, so we'll re-use this fallback.