Char[] and byte[] ambiguity between bytes, str, and bytearray

[Thrameos]

One of the left over issues from Python 2 is the ambiguity between bytes, bytearray, and str when selecting the overload for byte[] and char[]. Simple commands like JString(bytearray([1])) currently fail with ambiguity between java.lang.String(char[]) and java.lang.String(byte[]). bytearray is pretty obviously best matched to byte[] but we have three implicit conversions defined that match ''PyUnicode'', ''PyBytes'', and ''PySequence''.

I would recommend modifying the matches to be
byte[] <=> str (none) reason: string to math type prohibited)
byte[] <=> bytes, bytearray (exact) reason: bytes are bytes
byte[] <=> Sequence (implicit) reason: a list of numbers can be converted
char[] <=> str (exact)
char[] <=> Sequence, bytes, bytearray (implicit)

Personally I think the last one should be "none" but it would break code.