Consider changing Char to represent a code point rather than a UTF-16 code unit #3662

Reference: pure-c/purec#34 (comment)

Exposing Char as UTF-16 code units is problematic for backends that need to use something other than UTF-16 as the underlying representation. Would it be better if Char was encoding agnostic and represented a code point? What would that mean for purescript-strings?