[close #378] *: add go:generate to building and testing process

[pingyu]

What problem does this PR solve?

Issue Number: close #378

Problem Description: cdc: No go generated in building and testing process

What is changed and how does it work?

• Add go-generate to building & testing process.
• Revert manually edit codes which are generated by msg, and move unit tests out.
• Fix build error of appdash-data. See reading https://sourcegraph.com/sourcegraph/appdash-data?go-get=1: 404 Not Found pulumi/pulumi#14873.

Code changes

Check List for Tests

This PR has been tested by at least one of the following methods:

• Unit test

Side effects

• No side effects

Related changes

• No related changes

To reviewers

Please follow these principles to check this pull requests:

• Concentration. One pull request should only do one thing. No matter how small it is, the change does exactly one thing and gets it right. Don't mix other changes into it.
• Tests. A pull request should be test covered, whether the tests are unit tests, integration tests, or end-to-end tests. Tests should be sufficient, correct and don't slow down the CI pipeline largely.
• Functionality. The pull request should implement what the author intends to do and fit well in the existing code base, resolve a real problem for TiDB/TiKV users. To get the author's intention and the pull request design, you could follow the discussions in the corresponding GitHub issue or internal.tidb.io topic.
• Style. Code in the pull request should follow common programming style. (For Go, we have style checkers in CI). However, sometimes the existing code is inconsistent with the style guide, you should maintain consistency with the existing code or file a new issue to fix the existing code style first.
• Documentation. If a pull request changes how users build, test, interact with, or release code, you must check whether it also updates the related documentation such as READMEs and any generated reference docs. Similarly, if a pull request deletes or deprecates code, you must check whether or not the corresponding documentation should also be deleted.
• Performance. If you find the pull request may affect performance, you could ask the author to provide a benchmark result.

(The above text mainly refers to TiDB Development Guide. It's also highly recommended to read about Writing code review comments)

[zeminzhou]

LGTM