Improvements for prettier auto formatter

[vnishukov]

Motivation and context

Make pre commit hook and auto format applicable to whole project, not only ui module
Also make fixes for json, yml, and md file formatting

How has this been tested?

Just make some changes in file of json, yml, md and try to commit

Checklist

• I submit my changes into the develop branch
• I have added description of my changes into CHANGELOG file
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (read github docs)
• I have increased versions of npm packages if it is necessary (cvat-canvas,
  cvat-core, cvat-data and cvat-ui)

License

• I submit my code changes under the same MIT License that covers the project.
  Feel free to contact the maintainers if that's a concern.
• I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

[coveralls]

Coverage remained the same at 66.695% when pulling e7f0b3b on prettier_improvements into 29170ca on develop.

[nmanovic]

@bsekachev , it looks fine for me. If you are OK as well, please merge.

[bsekachev]

@nmanovic @vnishukov

As I said in other PR #2311, it doesn't look well when I need to change only a couple of lines of code and precommit brings a lot of change per every modified file. In this PR for example I changed 4-10 lines of code, but PR shows almost 300 changes

It makes code review difficult and not obvious what changes in the code directed to solve an issue. It especially becomes difficult to review when we introduce big features (like projects from Dmitri), because of too much extra code changes not related with PR.

Can we do something with it? (I would suggest run automatic linter checks & fixes only for changed rows in a PR). Now I have to disable this feature in my patches by removing corresponding lines from package.json

[vnishukov]

Need additional discussion