Different 'character_set_server' values in src and dest,may cause different character set

[Dinosauria]

Description

当源端和目标端character_set_server值不同时，当创建schema不指定character set 和collation，源端和目标端创建schema的默认字符集有差别，在此情况下当该库内不指明字符集 创建table时，会导致table继承schema的字符集，job创建之初时，log中有这一句不知为何没有生效

2018/11/08 13:24:46.097236 [INFO] [87651bc5-df8e-f2fe-dbf2-0afaa3c3e73a] mysql.extractor: Step 5: committing transaction 
2018/11/08 13:24:46.097462 [DEBUG] [87651bc5-df8e-f2fe-dbf2-0afaa3c3e73a] mysql.applier: Exec [SET collation_server = utf8mb4_general_ci, character_set_server = utf8mb4] 

Output of ./dtle version:

Dtle 9.9.9.9 (git: master c5126693689180c0950969432e4f939232f2dda8)

Additional information you deem important (e.g. issue happens only occasionally):

Additional details (log, config, job config etc):

1. job.json

{
    "Name":"task1",
    "Failover":false,
    "Orders":[],
    "Type":"synchronous",
    "Tasks":[
        {
            "Type":"Src",
            "NodeId":"53c0746e-beda-b193-ddbd-2744696b54a0",
            "Config":{
                "Gtid":"",
                "SkipCreateDbTable":false,
                "ExpandSyntaxSupport":false,
                "DropTableIfExists":false,
                "ReplChanBufferSize":"600",
                "ChunkSize":"2000",
                "ApproveHeterogeneous":true,
                "ReplicateDoDb":[],
                "ConnectionConfig":{
                    "Host":"172.17.5.1",
                    "Port":"1111",
                    "User":"test",
                    "Password":"test"
                }
            }
        },
        {
            "Type":"Dest",
            "NodeId":"53c0746e-beda-b193-ddbd-2744696b54a0",
            "Config":{
                "SkipCreateDbTable":false,
                "DropTableIfExists":false,
                "ExpandSyntaxSupport":false,
                "ReplChanBufferSize":"600",
                "ApproveHeterogeneous":true,
                "ConnectionConfig":{
                    "Host":"172.17.5.2",
                    "Port":"2222",
                    "User":"test",
                    "Password":"test"
                }
            }
        }
    ]
}

2. dtle.log:dtle_log.txt

Experiment 1

On a mysqld with character_set_server='latin1'.

SET collation_server = utf8mb4_general_ci, character_set_server = utf8mb4;
> create schema bbb2;
...
> show create schema bbb2;
| bbb2     | CREATE DATABASE `bbb2` /*!40100 DEFAULT CHARACTER SET utf8mb4 */ |

Guess: SET ... is not executed on all connection.

050ece3 should fix the base case.

Further case: pause / resume job and try create schema and see its charset

bug in 050ece3: applier does not receive the DumpEntry for an incremental job (with Gtid set)

[yaqigithub]

Verified in Dtle 9.9.9.9 (git: master 203100a)，but failed in full copy #349