feat(azure-open-ai): update model YAMLs [bot]

[models-bot]

Auto-generated by poc-agent for provider azure-open-ai.

---

Note

Low Risk
Catalog/metadata-only YAML changes with no logic or runtime behavior; cost numbers are equivalent after formatting.

Overview
Updates o3-mini.yaml to reflect deprecation: adds isDeprecated: true, sets status from active to deprecated, and keeps the existing deprecationDate.

Token cost fields are rewritten in scientific notation (e.g. 1.21e-6 instead of 0.00000121) across all regions; values are unchanged. removeParams drops quotes around the n entry for consistent YAML style.

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

[github-actions]

/test-models

[harshiv-26]

Gateway test results

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

Provider	Model	Scenarios

[cursor]

Cursor Bugbot has reviewed your changes 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 e41a66c. Configure here.}

[cursor]

Unquoted n may parse as boolean false

Low Severity

The previously quoted "n" in removeParams was changed to bare n. In YAML 1.1 parsers (e.g., PyYAML, Ruby YAML), bare n is interpreted as boolean false rather than the string "n". While the project's own build tooling uses YAML 1.2 parsers (js-yaml 4.x, yaml 2.x) where this is fine, any downstream YAML 1.1 consumer would silently get the wrong type. Most other files in this directory consistently keep "n" quoted for this reason.

 

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