feat: add a pre-commit hook

[AliSajid]

This pull request introduces a pre-commit hook for validating Browserslist configurations. The most important changes include the addition of a configuration file for the pre-commit hooks. There are also relevant additions to the README.md.

Pre-commit hook addition:

• pre-commit-hooks.yaml: Defined a new hook, browserslist-lint, to validate Browserslist configurations using npx browserslist-linter. This hook is triggered by changes to .browserslistrc or package.json.

Documentation updates:

• README.md: Added a section on the pre-commit hook, including instructions on how to add it to the pre-commit configuration.

[ai]

For what tool we need this YAML file? Can you explain me a little more?

[AliSajid]

This yaml implementation is a part of the pre-commit configuration. pre-commit is an open source framework that lets people deploy different packages for checks before they commit something toa. git repository. It is widely adopted and is practically an industry standard.

You can see the following pre-commit enabled repositories:

• https://github.com/pre-commit/mirrors-eslint
• https://github.com/rbubley/mirrors-prettier

The pre-commit-hooks.yaml file allows a pre-commit user to include browserslist-linting as a part of their workflow. It does not change anything in the package itself. An end user, such as myself, can then include this as part of their suite of pre-commit checks by the two lines as follows:

repos:
	repo: https://github.com/browserslist
	hooks:
		- id: browserslist-lint

[ai]

Let’s add link here. pre-commit is a popular name, there are many projects with this name. People will now understand it without a link.

[ai]

Let’s use 2 space indents to have consistent code style