chore: enforce lint in pre commit hook

[weitingsun]

Description

To enforce prettier and Eslint in pre commit hook

Related issues

#16371

Manual testing steps

1. Pull this PR
2. In a tsx file, try to add a space or remove one in any lines
3. Find an useEffect and remove one of the dependencies
4. Commit the changes locally, you should see the pre commit checks which will enforce prettier and give error messages for ESLint

Screenshots/Recordings

Before

No pre commit checks

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​husky@​1.3.1 ⏵ 9.1.7	+10		-41

View full report

[socket-security]

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring alerts on:

• npm/[email protected]

View full report

[weitingsun]

@SocketSecurity ignore npm/[email protected]

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 8639a87
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b49bf435-2e59-4780-afc9-8d8573c861c2

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud