[BUG] Intent Creation/ Update Fails with Estonian Characters

[matKlju]

Bug description:

When activating a service whose service name contains Estonian special characters (e.g., ö, õ, ü, ä), the intent detection logic fails to update the intents file in the storage blob.

As a result:

• The intents file is not written or updated correctly
• The intent detection pipeline cannot resolve the intent
• The chatbot request remains hanging without a response

This occurs specifically during the service activation step, when the system attempts to update the intent definitions associated with the service.

Expected behavior:

Services containing Estonian special characters in the service name should activate normally.

The system should:

• Successfully update the intents file in the storage blob
• Properly register the intent for detection
• Allow the chatbot to resolve the intent and return a response

Screenshots:
Ruuter log:

Chat status:

Additional information:

Issue appears related to encoding or filename handling when generating or updating the intents file during activation.

Services with ASCII-only names work correctly, while services containing characters such as ö, õ, ü, or ä consistently cause the intent update step to fail.