possibly wrong error returned when changing charset to an unsupported charset

Driver support session state changed.
In case connection charset is changed to an unknown charset (Charset are normally all known, but in case MySQL add a new charset that is temporary unknown to driver), driver must then throw an exception. That error was not thrown, sue to an error (reported as https://github.com/mariadb-corporation/mariadb-connector-nodejs/issues/177)