Fix Bad logic to decode the column name #1413

[testn]

Introduce character_set_results tracking to ensure that we can read the column name properly

still in the draft mode

[testn]

@sidorares this is the first attempt trying to fix #1413. It is still rough but it should demonstrate what we can address this problem.

[sidorares]

test/integration/connection/encoding/test-track-encodings.js test fails, not sure if your change discovered legitimate error

[testn]

@sidorares that exposes the problem that I'm working on a fix. Basically, when you specify character_set_client, you have to encode your SQL in that encoding as well.