Add custom URL option for Requesty provider

[requesty-JohnCosta27]

What specific problem does this solve?

Allow the user to set a custom URL for the provider Requesty. This is something we're working on over at Requesty, and it would be useful for users to be able to do this.

Additional context (optional)

No response

Roo Code Task Links (Optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear impact and context

Interested in implementing this?

• Yes, I'd like to help implement this feature

Implementation requirements

• I understand this needs approval before implementation begins

How should this be solved? (REQUIRED if contributing, optional otherwise)

Following the pattern from the other providers. Adding a checkbox "Use custom URL", and clicking it makes a textbox appear. Requesty will then use this URL.

If the user unselects, or deletes this custom URL, we should go back to the default requesty URL.

How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)

Using a custom requesty deployment, such as localhost, or region specific. And the corresponding API key.

Technical considerations (REQUIRED if contributing, optional otherwise)

Keeping the code in line with the rest of the codebase, and not polutting anything outside of the requesty components.

Trade-offs and risks (REQUIRED if contributing, optional otherwise)

No response

[roomote]

Hi! I'm here to help out the maintainers and am going to work on implementing the custom URL option for the Requesty provider. I'll follow the existing patterns from other providers to add a checkbox for "Use custom URL" with a corresponding text input field. Thanks for the clear requirements!

[roomote]

I've successfully implemented the custom URL option for the Requesty provider! 🎉

The pull request is ready for review: #6984

Summary of changes:

• Added a "Use custom base URL" checkbox in the Requesty provider settings (following the same pattern as OpenRouter)
• When checked, a text field appears for entering the custom Requesty URL
• The provider will use the custom URL for all API calls when configured
• If unchecked or cleared, it reverts to the default Requesty URL
• All tests pass and the implementation is fully backward compatible

This allows users to connect to custom Requesty deployments such as localhost or region-specific instances as requested. The implementation keeps the code clean and follows the existing patterns in the codebase.

[daniel-lxs]

Closed by #6992