chore: Dev to Main merge

[Ragini-Microsoft]

Purpose

This pull request updates the default image generation model throughout the codebase and documentation from gpt-image-1 to gpt-image-1-mini. The change ensures consistency across deployment scripts, environment variables, and user guides, and reflects the new recommended model for image generation. Existing references to gpt-image-1 are replaced with gpt-image-1-mini, including validation logic and quota guidance.

Deployment and environment configuration updates:

• Changed the default value and allowed options for image_model_choice in .github/workflows/deploy-orchestrator.yml, .github/workflows/deploy-v2.yml, and .github/workflows/job-deploy.yml to use gpt-image-1-mini instead of gpt-image-1. Validation logic and environment variable assignments were also updated accordingly. [1] [2] [3] [4] [5] [6]
• Updated content-gen/.env.sample to set AZURE_AI_IMAGE_DEPLOYMENT and AZURE_OPENAI_IMAGE_MODEL defaults to gpt-image-1-mini, and clarified supported models and settings. [1] [2]
• Modified content-gen/README.md to reflect gpt-image-1-mini as the default image model in the configuration table.

Documentation and user guide improvements:

• Updated deployment guides (content-gen/docs/AZD_DEPLOYMENT.md, content-gen/docs/DEPLOYMENT.md, content-gen/docs/CustomizingAzdParameters.md) to reference gpt-image-1-mini as the default and recommended image model, including quota requirements, parameter tables, and troubleshooting steps. [1] [2] [3] [4] [5] [6] [7]
• Revised content-gen/docs/IMAGE_GENERATION.md to describe image generation with gpt-image-1-mini, update diagrams and tables, and clarify environment variable usage. [1] [2] [3] [4]

Troubleshooting and quota guidance:

• Updated troubleshooting documentation to include gpt-image-1-mini in the list of restricted Azure OpenAI models requiring quota access requests.
• Adjusted pricing and quota references in the main README.md to indicate the new default model.

These changes collectively ensure that gpt-image-1-mini is the default and recommended image generation model across deployment, configuration, and documentation.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.