[PROPOSAL] Enforcing coding conventions and formatting with Husky pre-commit hooks

[CCongWang]

What is the problem? What is preventing you from meeting the requirements?
prettier was added in #70, and was integrated with ESLint to apply coding conventions and formatting rules to the project in #186. However, contributors need to manually run the lint command to lint and fix the code, if we don't run them regularly, we see inconsistent code formatting around the project.

What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?
We can utilize Husky pre-commit hooks to run lint command and formatting check automatically, to make sure code changes in each commit are consistent in coding conventions and formatting.

[seraphjiang]

add small request, could we add the pre-commit setup/usage to
https://github.com/opensearch-project/opensearch-dashboards-functional-test/blob/main/CONTRIBUTING.md

[CCongWang]

@joshuali925 @ohltyler @davidcui1225 @bowenlan-amzn @annie3431

Hi plugin owners, we plan to use precommit hook to run lint command automatically, the goal is to make the code styles and formatting consistent, please check out the PR and updated Formatting section in CONTRIBUTING. Let me know if you have questions/concerns/suggestions! Thanks!