Updating Gemini and Vertex AI model's naming convention for `gemini-2.5-pro-preview-{dates}` to `gemini-2.5-pro`

[HahaBill]

What specific problem does this solve?

In Roo Code, we still use these naming conventions: gemini-2.5-pro-preview-{dates}.

However, this is being replace by the gemini-2.5-pro according to this documentation:

• https://ai.google.dev/gemini-api/docs/models#experimental-models
• Same goes for Vertex AI: https://ai.google.dev/gemini-api/docs/models#gemini-2.5-pro

Currently in Roo Code, you can see here that we have some older naming conventions:

• Gemini: https://github.com/RooCodeInc/Roo-Code/blob/main/packages/types/src/providers/gemini.ts
• Vertex: https://github.com/RooCodeInc/Roo-Code/blob/main/packages/types/src/providers/vertex.ts

Summary

As a first step, I am proposing to only change/delete preview versions to only gemini-2.5-pro for both Gemini and Vertex AI.

The reason is that the preview versions currently are being replaced/removed by GA versions and will be less used in the future. Also, the simpler the better.

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)

Replacing gemini-2.5-pro-preview-{dates} version to gemini-2.5-pro in here:

• Gemini: https://github.com/RooCodeInc/Roo-Code/blob/main/packages/types/src/providers/gemini.ts
• Vertex: https://github.com/RooCodeInc/Roo-Code/blob/main/packages/types/src/providers/vertex.ts

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

Given I have a tasks/feature to implement and I want to use Gemini 2.5 Pro
When I put a prompt in the chat and hit enter
Then everything should work as expected
And I see the model's response in the chat, token count, etc.
But the Roo Code has not receive the model response or it shows an error that Gemini 2.5 preview versions do not exist

Technical considerations (REQUIRED if contributing, optional otherwise)

I am thinking about just to remove the gemini-2.5-pro-preview-{dates} versions but it could have an impact in the provider settings where users chose preview versions before.

The solution would be to add a logic to do progressive migration to gemini-2.5-pro. On the UI side we will not show preview versions anymore but in the backend side we will handle legacy preview Gemini 2.5 pro versions.

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

The risk could be that users chose gemini-2.5.pro-preview-{dates} before but then the backend could not find it -> as stated before, this will be handled.

[roomote]

PR #5446 has been created to address this issue: #5446