feat: add Poe.com as an LLM provider

[roomote]

Summary

This PR adds support for Poe.com as an LLM provider in Roo-Code. Poe provides an API that is fully compatible with the OpenAI Chat Completions format, allowing users to access a wide variety of models including GPT, Claude, Gemini, Llama, Mistral, and more through a single API.

Changes

• Added Poe provider type definitions with support for 20+ models
• Implemented PoeHandler extending BaseOpenAiCompatibleProvider
• Added Poe to provider settings schema and API handler
• Included comprehensive tests for Poe provider functionality
• Added support for custom Poe bots with default model info
• Updated webview UI to handle Poe provider selection

Benefits

• Users can access multiple LLM models through a single Poe API key
• Reduces the need to manage multiple provider accounts
• Supports both predefined models and custom Poe bots
• Fully compatible with existing OpenAI-style API infrastructure

Testing

• All provider tests pass successfully
• Type checking passes
• Linting passes

Closes #6594

---

Important

Adds Poe.com as an LLM provider, integrating it into the existing infrastructure with support for multiple models and custom bots.

• Behavior:
  • Adds PoeHandler in src/api/providers/poe.ts extending BaseOpenAiCompatibleProvider to handle Poe API interactions.
  • Updates buildApiHandler() in src/api/index.ts to include PoeHandler for "poe" provider.
  • Supports 20+ models and custom bots with default model info.
• Provider Settings:
  • Adds "poe" to providerNames and providerSettingsSchema in provider-settings.ts.
  • Defines poeSchema for Poe-specific settings.
• UI:
  • Updates useSelectedModel() in useSelectedModel.ts to handle Poe provider selection.
• Tests:
  • Adds poe.spec.ts for testing PoeHandler functionality, including model selection and API interactions.

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

[roomote]

I reviewed my own code and found it suspiciously adequate.

[roomote]

I notice that other recent providers have i18n entries for their API keys (e.g., groqApiKey), but this PR doesn't add translations for poeApiKey and poeBaseUrl. Is this intentional, or should we add i18n entries for consistency?

I see that the English common.json doesn't have a providers section, so perhaps this is following a different pattern?

[roomote]

Consider adding URL validation for poeBaseUrl similar to other providers. Currently it accepts any string, but validating it as a proper URL could prevent configuration errors:

Suggested change

	poeBaseUrl: z.string().optional(),
	poeBaseUrl: z.string().url().optional(),

[roomote]

The pricing information looks comprehensive! Is this pricing data current and accurate? It might be helpful to add a comment indicating the source of this pricing information and when it was last updated, to help with future maintenance.

[roomote]

Great test coverage! Consider adding a few edge case tests:

• Invalid API key handling (401/403 responses)
• Network timeout scenarios
• Malformed response handling from the Poe API

These would help ensure robust error handling in production.

[roomote]

Consider making the API documentation link more prominent with a JSDoc comment:

Suggested change

	export class PoeHandler extends BaseOpenAiCompatibleProvider<PoeModelId> {
	/**
	* Poe API Handler - Provides access to multiple LLM models through Poe's OpenAI-compatible API
	*
	* API Documentation: https://creator.poe.com/docs/external-applications/openai-compatible-api
	*
	* Supports both predefined models (GPT, Claude, Gemini, etc.) and custom Poe bots.
	*/
	export class PoeHandler extends BaseOpenAiCompatibleProvider<PoeModelId> {