Looking for advice on the 400 Bad Request error hitting the /api/v2/bots/{botId}/intents endpoint when trying to map Zendesk macro tags to Genesys Cloud intents via the migration script. The payload structure mimics the Zendesk API format, but Genesys Cloud rejects the synonyms array, claiming invalid characters unlike the flexible tagging system we used in Zendesk. Is there a specific sanitization step required for the intent phrases before the POST request?