feat(google-vertex): update model YAMLs [bot]

[models-bot]

Auto-generated by poc-agent for provider google-vertex.

---

Note

Low Risk
Single provider model catalog YAML change affecting billing metadata and advertised capabilities; no application code paths.

Overview
Updates google/gemini-3-pro-image catalog metadata to match current Google docs: status moves from preview to active, and a second sources link to the Gemini API model page is added.

Costs are adjusted slightly (input_cost_per_image 0.0011 → 0.00112) and batch input/output token cost fields are removed from the global pricing block. Features drop function_calling and tool_choice, leaving system_messages and structured_output.

^{Reviewed by Cursor Bugbot for commit 39a7e61. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

/test-models

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 39a7e61. Configure here.}

[cursor]

Missing batch token cost fields

Medium Severity

This commit drops input_cost_per_token_batches and output_cost_per_token_batches from the global cost entry while other Vertex Gemini image models (including google/gemini-3-pro-image-preview and google/gemini-2.5-flash-image) still declare the usual half-rate batch fields. Downstream cost logic that reads batch rates from this catalog will fall back or omit batch pricing for google/gemini-3-pro-image, producing wrong estimates for Vertex batch jobs.

 

^{Reviewed by Cursor Bugbot for commit 39a7e61. Configure here.}

[harshiv-26]

Gateway test results

• Total: 1
• Passed: 0
• Failed: 0
• Validation failed: 0
• Errored: 0
• Skipped: 1
• Success rate: 0.0%

Provider	Model	Scenarios
google-vertex	google/gemini-3-pro-image	skipped: skip-check

Skipped (1)

google-vertex/google/gemini-3-pro-image — skip-check (skipped)

Skip reason

unsupported mode 'image'