Uyghur language script glyph error.

Nobody has claimed this yet.

Hey, when using Mapbox studio [Uyghur-language script](https://en.wikipedia.org/wiki/Uyghur_Arabic_alphabet) appears to have shaping errors for the RTL text glyphs. Unsure what causes the error in some characters and not others (I don't speak Uyghur'che, but colleagues who do tell me it's not strictly the characters which vary from Arabic where the issue occurs) perhaps it's a specific unicode range, I believe Uyghur script is spread over four unicode ranges - Arabic, Arabic Suppliment and Arabic Presentation Forms A/B.
Essentially, for a number of charcters mapbox uses its final placement form no matter where in the word it occurs. For example, the place name for Kizilsu (قىزىلسۇ) renders like this 
Where the ى character (among others) renders in the final form rather than the medial form.
The problem is as it appeared in the 'wrong' frame of the first gif in [this](https://blog.mapbox.com/improving-arabic-and-hebrew-text-in-map-labels-fd184cf5ebd1) blog post.
It would be great to get this language supported, we have a dataset of 16,000+ (only 500 translated into Uyghur so far) place names for Xinjiang that we use for a [map](https://xjdp.aspi.org.au/map/) tracing the human rights abuses against Uyghur people. Their culture and language is being erased in China, it would be neat if Mapbox could help preserve it!
Thanks,
Nathan.

Reproduce the issue in Mapbox Studio with the Uyghur place name قىزل... and compare its contextual glyph forms. Start by tracing the RTL text-shaping path for the Arabic, Arabic Supplement, and Arabic Presentation Forms ranges mentioned in the report. Done means the example and other Uyghur text render with the correct contextual forms.

Written by the indexing model from the issue text.