Fix charset

[Groruk]

Close #506
Close #505
Fix #236
Fix #390

Description

SQL_SetCharset seems to be bugged and defaults to latin1 as a charset. To fix this we are now using "SET NAME" queries exclusively (until a fix for SQL_SetCharset is found)

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.

[CrazyHackGUT]

This is very dumb fix ever i seen.
MySQL extension can't escape characters properly, if character set is changed with simple query.
You need think about this "fix" and revert PR until someone started having problems.

[Bara]

And Sourcemod 1.9 and lower don't support utf8mb4.

Here's the link to the message:
https://discordapp.com/channels/335290997317697536/335290997317697536/504723911854915585

[CrazyHackGUT]

Maybe instead of a hasty merging of PR, you give some time for another users for testing?
I don't see any reasons for using PR, if no one can't review their before merging.

Think about it, @Groruk. And, please, stop merging PR without reviews.