fix: retry mechanism for status error message

[Shreyas-Microsoft]

Purpose

This pull request introduces improvements to the Azure environment configuration and enhances the retry logic for processing queue messages in the content processing pipeline. The main focus is on providing clearer status updates during transient failures and ensuring the workflow continues to retry before marking a process as failed.

Environment configuration updates:

• Added new Azure-related environment variables to the .env file in infra/vscode_web to support agent, environment, and project resource configuration.

Queue processing and retry logic improvements:

• Updated the queue handler in queue_handler_base.py to set the process status to "Retrying" (instead of immediately to "Error") when a message has retries remaining (up to 5 attempts), allowing the workflow poller to continue waiting for successful processing.
• Ensured that only after all retries are exhausted does the process status change to "Error" and the message is moved to the Dead Letter Queue.

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.

What to Check

Verify that the following are valid

• ...

Other Information