feat: add azure as first class provider

[louis-jan]

Describe Your Changes

This PR adds Azure as a first-class provider where users can specify the base URL and key in settings.

Users accessing the model providers screen will see the Azure provider to specify resource names and deployments (models).

Then they can chat with deployments (models)

Open questions:
Q: Why don't we add a new setting called "service name" instead of letting users edit the Base URL?
A: We can do this, but it's to ensure consistency with other providers. There might be multiple resources, and users may not know how to manually add a new Azure Provider. They can refer to this to create a new Azure OpenAI provider.

Fixes Issues

• Closes feat: Support for Azure #5342

Self Checklist

• Added relevant comments, esp in complex areas
• Updated docs (for bug fixes / features)
• Created issues for follow-up changes or refactoring needed

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 71f684e in 2 minutes and 21 seconds. Click for details.

• Reviewed 177 lines of code in 5 files
• Skipped 1 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. web-app/src/consts/providers.ts:59

• Draft comment:
  Azure provider object added. Structure and settings follow existing providers; verify base URL and docs link accuracy.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. web-app/src/containers/dialogs/AddModel.tsx:52

• Draft comment:
  Optional chaining added on providerModels access for supportsToolCalls and supportsImages improves null-safety.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

3. web-app/src/lib/utils.ts:31

• Draft comment:
  Azure provider logo added in getProviderLogo ensuring consistent visuals for all providers.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

4. web-app/src/services/providers/tauri.ts:36

• Draft comment:
  Optional chaining for supportsToolCalls and supportsImages in Tauri service adds robustness when providerModels data is missing.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

5. web-app/src/services/providers/web.ts:94

• Draft comment:
  Optional chaining and improved error handling in WebProvidersService enhance safety and clarity in model fetch logic.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_y7MrZq1LFzCrAjyw

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[github-actions]

Barecheck - Code coverage report

Total: 30.39%

Your code coverage diff: 0.11% ▴

Uncovered files and lines

File	Lines
web-app/src/containers/dialogs/AddModel.tsx	1, 10-19, 26-31, 34-36, 39-42, 45-50, 52-57, 59-67, 70-74, 77-79, 81-87, 89-95, 97-104, 107-110, 112-126, 129-135, 137-143, 146-150, 152-156, 158
web-app/src/lib/utils.ts	12, 18, 20, 22, 24, 26, 32, 41, 51, 96-98
web-app/src/services/providers/tauri.ts	5-12, 14-15, 17-18, 20-27, 29-31, 33-34, 36-41, 43-55, 57-61, 63-85, 88-90, 92-101, 103-104, 106-135, 137-142, 144-147, 149-152, 156-161, 164-167, 170-173, 175, 177-194, 196, 199, 201-204, 206-211, 213-223, 226-231, 233-240, 243-247, 250-254, 256-281
web-app/src/services/providers/web.ts	27, 47, 49, 77-78, 99, 155-158, 214, 243-244

[Minh141120]

LGTM on Windows