Revert "feat: Experiment: Show a bit of stats in Cloud tab to help users discover there's more in Cloud"

[mrubens]

Reverts #8415

---

Important

Reverts feature adding usage statistics to Cloud tab, removing related code, UI elements, and localization strings.

• Behavior:
  • Reverts feature that added usage statistics to the Cloud tab, removing getUsagePreview() from CloudAPI.ts and related UI elements from webviewMessageHandler.ts.
  • Removes usage statistics UI components from CloudView.tsx and UsagePreview.tsx.
• Imports and Logging:
  • Cleans up imports in CloudAPI.ts and ContextWindowProgress.spec.tsx.
  • Removes logging related to usage statistics in CloudAPI.ts and ChatRow.tsx.
• Localization:
  • Removes usage statistics related localization strings from various language files.
• Misc:
  • Removes formatCost function from format.ts and related mock in TaskHeader.spec.tsx.

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

[ellipsis-dev]

Typo/lexical note: The <span> now contains ${totalCost?.toFixed(2)}, which in JSX will be treated as a string rather than an evaluated expression. If the intention is to display the cost with a preceding currency symbol, consider using curly braces to embed the JS expression, for example:

{$${totalCost?.toFixed(2)}}

This change would ensure that the value is properly computed and displayed.

Suggested change

	<span>${totalCost?.toFixed(2)}</span>
	<span>{`$${totalCost?.toFixed(2)}`}</span>

[roomote]

I found an issue that needs attention in this revert.

[roomote]

P1: Fallback from response.json() to response.text() can fail because the body stream is single-use. After json() throws due to invalid JSON, the stream is consumed and text() may throw ("body used already"). To robustly capture error bodies, read text once and JSON-parse it, or clone() before consuming. The previous implementation used response.text() then JSON.parse fallback which avoids this pitfall.