Predictions.convert : Request to support custom terminologies

[DanBloy]

Is your feature request related to a problem? Please describe.
Currently predictions.convert (Translate text) does not support custom terminologies. The Translate API does support custom terminologies. Therefore currently when using Amplify and needing to use custom terminologies, we cannot use the Amplify provided prediction library.

Describe the solution you'd like
Predictions.convert to support custome terminologies

Current payload:

translateText: { source: { text: textToTranslate, language : "es" }, targetLanguage: "en" } )

Requested paylod:

translateText: { source: { text: textToTranslate, language : "es" }, targetLanguage: "en", terminologyNames": [ "string" ], } )

Describe alternatives you've considered
Currently having to use the Amazon Translate API which works, however, this requires additional infrastructure such as an API Gateway and Lambda

Additional context
None