i18N: Fix,Change and union the Chinese translations in different files

[ghost]

Change Logs:

1. Fix: Move the comments into JSON's body to avoid JSON's parsing error
   (i18n/chs/src/vs/base/common/json.i18n.json).

A right example is i18n/chs/src/vs/base/common/errorMessage.i18n.json

2. Change and Union:

Because this error means you have invalid EOF symbols. It would be better we can translate it more clearly (such as in js or C#, we've missed "}" at the end of code).

What's more, it's NOT so easy and simple to understand what '预期的文件结尾' is (This translation just comes from English words one by one "End Of File" and "Expected", which is hard to understand), what we should do is to notify users what they've missed.

BTW: There are two places having the different translation for "error.endOfFileExpected", so I've unioned them all together in this submit.

1. i18n/chs/src/vs/base/common/json.i18n.json
2. i18n/chs/src/vs/base/common/jsonErrorMessages.i18n.json

[msftclas]

All CLA requirements met.

[ghost]

@danyeh : I've fixed some issues in the i18N's JSON and update Chinese translations. Please see in details in Change Logs I've updated below.

[danyeh]

Thanks @MaleDong for your feedback! I have merged your change in.
However, any change to localization should be made in Transifex. Plus we are moving to Language Pack as extension model.
Visit https://aka.ms/vscodeloc for information of VS Code community localization program. And language pack extension

[ghost]

OK next time I'll submit there:)