fix(provider): bump Azure SDK to 3.0.93

[opencode-agent]

Issue for this PR

Azure still uses its own OpenAI SDK 3.0.84 dependency, so the direct OpenAI SDK update does not update Azure's GPT-6 capability handling.

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

Bumps @ai-sdk/azure from 3.0.88 to 3.0.93 in opencode and core, bringing its OpenAI SDK to 3.0.88, DeepSeek to 2.0.50, and provider-utils to 4.0.40.

Only the two manifests and lockfile change. No source edits, dependency patches, or added tests. The extra gateway lock records preserve its existing dependency versions.

The audited release changes are:

• Standard Schema optional-converter typing/error handling and an onInputStart documentation update in provider-utils.
• Native, strict-by-default JSON Schema for the SDK's dedicated azure.deepseek() factory; built-in OpenCode Azure routing does not call that factory.
• OpenAI tool-search result-ID replay and model-family/image defaults already included in OpenAI 3.0.88.

This intentionally retains upstream tier filtering. The new model-name parser fixes GPT-6-named deployments but also stops matching some old prefix-style deployment aliases; changing the filtering logic is left for a separate follow-up.

How did you verify your code works?

• Audited every intermediate Azure/DeepSeek release and reverified the inherited OpenAI/provider-utils artifacts, including registry integrity, source, generated bundles, types, maps, and dependency contracts. No unexplained implementation changes found.
• 795 selected existing OpenCode/Core tests passed with an isolated provider environment, covering Azure auth, provider selection, transforms, session LLM, transport errors/timeouts, and gateway behavior.
• Both packages passed bun typecheck; frozen-lockfile install, formatting, and diff checks passed.
• Local before/after request captures through OpenCode confirmed GPT-6 Priority forwarding in Responses and Chat and checked the deployment-name compatibility differences. No live Azure requests or production build.

Screenshots / recordings

Not applicable; no UI changes.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

Requested by: @rekram1-node (Aiden via Slack)