[AI] Integration Test fix

[paulb777]

Fix thinking budget test for Gemini 3. Thinking levels are recommended/supported, but keeping these tests for now as they pass.

#no-changelog

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

[paulb777]

/gemini review

[gemini-code-assist]

Code Review

This pull request removes several integration test cases for generateContentThinking that use thinkingBudget with the gemini3_1_FlashLitePreview model. This aligns with the description, which indicates that thinkingLevel is the recommended configuration for this model, making the removed tests obsolete. The change is a straightforward and correct test suite maintenance task.

[andrewheard]

Thanks! LGTM as is (feel free to ignore the proposed alternative).