[ISSUE #845] support standard json

[yuz10]

What is the purpose of the change

#845

because apache/rocketmq#4432 change route info to standard json such as:
{"brokerDatas":[{"brokerAddrs":{"0":"127.0.0.1:10911"}]}
the old is:
{"brokerDatas":[{"brokerAddrs":{0:"127.0.0.1:10911"}]}

Brief changelog

XX

Verifying this change

XXXX

Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

• Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when a cross-module dependency exists.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

[lizhanhui]

Is it possible to change the deserialization workflow as follows?

1. Attempt to parse the response JSON using standard go JSON library;
2. Check and catch potential errors, fallback to manual parsing if invalid contents are found;

[zhouxinyu]

Can we deserialize JSON string in a standard way? Make the SDK could handle both the two formats.

[yuz10]

I am afraid we cant use the standard way because the json is not standard, the change have already handled both stardard hand non-stardard formats

[yuz10]

Is it possible to change the deserialization workflow as follows?

1. Attempt to parse the response JSON using standard go JSON library;
2. Check and catch potential errors, fallback to manual parsing if invalid contents are found;

I think it is worthless to Attempt the first time to parse standard json, because in most case it will fail. the manual code is ugly but unfortunately we cant remove it, and its solid.

[ShannonDing]

according to apache/rocketmq#4471 , i will close this pr first.

[lizhanhui]

@yuz10 I am assuming this pull request works for both standard and illegal JSON responses. Right?