[feat] Team code format tool are not unified.

[ModestYjx]

We can set a standard during "git commit".There is a lot useful tool to deal with this problem.
eg: git提交代码时自动遵守eslint+prettier规范格式化代码

[ModestYjx]

Add a code reformat installation tutorial to "./doc/developer-totorial.md" and link to README.

[zhicheng-ning]

I just checked some information about the eslint and prettier. It seems that eslint and prettier are both front-end code formatting tools, especially for javascript. Besides, for code formatting, I usually directly use the shortcut keys that come with the IDE, so I'm not sure what is the purpose of configuring this thing.

[ModestYjx]

A good question!
For example, @BlueEmmaBlue likes using VSCODE, @zhicheng-ning likes using IDEA. If you are both reformat the code through IDE, it will result in too many redundant differences between a PR and we will don't clear what you modify. We will see many reformated codes in the changes of the PR.

[ModestYjx]

@zhicheng-ning Before, I am using "pre-commit" to reformat the code during "git commit". "eslint" is only an eg, you can choose the best one to install.
references:
https://blog.csdn.net/wuheshi/article/details/104628747/