fix: create new Requesty profile during OAuth

[Thibault00]

Fixing requesty oauth flow

---

Important

Fixes Requesty OAuth flow by creating a new profile with a fixed name and default model ID in ClineProvider.ts.

• Behavior:
  • In ClineProvider.ts, handleRequestyCallback() now creates a new Requesty profile with a fixed name "Requesty" and default model ID requestyDefaultModelId.
  • Removes usage of apiConfiguration and currentApiConfigName from getState() in handleRequestyCallback().
• Misc:
  • Simplifies the Requesty OAuth flow by directly setting the profile name and model ID.

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

[roomote]

Review Summary

Issues Found: 1

Issues to Address:

• Preserve base provider settings when creating Requesty profile (diffEnabled, fuzzyMatchThreshold, rateLimitSeconds, etc.)

---

Review completed by Roo Code PR Review

[roomote]

This implementation creates a Requesty profile without preserving base provider settings (like diffEnabled, fuzzyMatchThreshold, rateLimitSeconds, consecutiveMistakeLimit, etc.) that users may have customized. Unlike the OpenRouter (line 1414) and Glama (line 1447) handlers which spread apiConfiguration to preserve these settings, this creates a minimal configuration with only Requesty-specific fields. Consider preserving user preferences: { ...apiConfiguration, apiProvider: "requesty", requestyApiKey: code, requestyModelId: requestyDefaultModelId }

[mrubens]

@Thibault00 what do you think of this? Would it cause any issues to preserve the apiConfiguration like the others?