Add Azure Storage Bypass Configuration

[matKlju]

AS A System administrator
I WANT to control whether service configuration JSON is uploaded to Azure Blob Storage
SO THAT deployments can bypass Azure Storage integration when it is not required

##Description
Currently, saving a service or changing its status to Active sends the current service configuration JSON to Azure Blob Storage. The LLM later uses this JSON to read service metadata such as example questions, description, and title for intent detection.

Add a deployment configuration setting to control this behavior.

##Acceptance Criteria

• New configuration setting is added.
• Default value is "true".
• When set to "true", service save/status activation uploads service configuration JSON to Azure Blob Storage.
• When set to "false", Azure Blob Storage upload request is skipped.
• Saving a service still works when Azure upload is bypassed/ disabled
• Changing service status to Active still works when Azure upload is bypassed. - no error visible
• Bypass behavior is documented for DevOps deployment configuration.

Notes

Suggested setting name: AZURE_STORAGE_ENABLED=true

AZURE_STORAGE_ENABLED=true → upload to Azure Blob Storage.
AZURE_STORAGE_ENABLED=false → skip the upload.

[matKlju]

NB! When deploying to INSA, the given AZURE_STORAGE_ENABLED variable has to be set to false

• INSA will only use MCQ services, no LLM, so skipping blob storage is a must.